Li Jiantao

**Name of the Vulnerable Software and Affected Versions** Pony Mail (Lua implementation) (affected versions not specified) **Description** Inconsistent interpretation of HTTP requests, known as HTTP Request/Response Smuggling, allows for admin account takeover. This occurs when a front-end server and a back-end server disagree on the boundaries of an HTTP request, potentially allowing an attacker to "smuggle" a request to the back-end. **Recommendations** Restrict access to the instance to trusted users. Find an alternative software solution.

**Name of the Vulnerable Software and Affected Versions** Softing edgeAggregator and Softing edgeConnector modules (affected versions not specified) Softing edgeConnector Modbus (affected versions not specified) Softing edgeConnector 840D (affected versions not specified) Softing edgeConnector Fanuc CNC (affected versions not specified) Softing edgeConnector Siemens (affected versions not specified) **Description** The issue is related to the transmission of credentials in cleartext, which may allow a remote attacker to capture packets and craft their own requests, potentially leading to unauthorized access to protected information. This could enable an attacker to bypass authentication. **Recommendations** For Softing edgeAggregator, consider disabling the transmission of credentials in cleartext until a patch is available. For Softing edgeConnector modules, restrict access to sensitive information to minimize the risk of exploitation. For Softing edgeConnector Modbus, Softing edgeConnector 840D, Softing edgeConnector Fanuc CNC, and Softing edgeConnector Siemens, avoid using cleartext transmission of credentials in the affected API endpoints until the issue is resolved. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Bitrix24 version 22.0.300 **Description** An unsafe variable extraction issue exists in the `bitrix/modules/main/classes/general/user options.php` file. This allows remote authenticated attackers to execute arbitrary code through two methods: appending arbitrary content to existing PHP files, or PHAR deserialization. The issue involves incorrect external control of the file name or path. Exploitation may allow an attacker to execute arbitrary code and elevate privileges. **Recommendations** Bitrix24 version 22.0.300: At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Bitrix24 version 22.0.300 **Description** The issue is related to the lack of a mime type response header in Bitrix24, which allows authenticated remote attackers to execute arbitrary JavaScript code in the victim's browser. If the victim has administrator privileges, it is also possible to execute arbitrary PHP code on the server. This can be achieved by uploading a crafted HTML file through the "/desktop app/file.ajax.php?action=uploadfile" endpoint. **Recommendations** For Bitrix24 version 22.0.300, as a temporary workaround, consider disabling the upload functionality through the "/desktop app/file.ajax.php?action=uploadfile" endpoint until a patch is available. Restrict access to the `file.ajax.php` module to minimize the risk of exploitation. Avoid using this endpoint until the issue is resolved. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Bitrix24 version 22.0.300 **Description** The issue in Bitrix24 is related to global variable extraction in the bitrix/modules/main/tools.php component, allowing unauthenticated remote attackers to enumerate attachments on the server and execute arbitrary JavaScript code in the victim's browser. If the victim has administrator privileges, it is also possible to execute arbitrary PHP code on the server. This is achieved via overwriting uninitialized variables. **Recommendations** For Bitrix24 version 22.0.300, consider disabling access to the bitrix/modules/main/tools.php component until a patch is available. Restricting the use of uninitialized variables in this component can also help minimize the risk of exploitation. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Bitrix24 version 22.0.300 **Description** An improper file stream access issue exists in the `/desktop app/file.ajax.php?action=uploadfile` component of Bitrix24. This allows unauthenticated remote attackers to cause a denial-of-service condition by using a crafted `tmp url`. The issue is related to a loop with an inaccessible exit condition. The affected API endpoint is `/desktop app/file.ajax.php` with the `action` parameter set to `uploadfile`. The vulnerable parameter is `tmp url`. **Recommendations** Bitrix24 version 22.0.300: At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Bitrix24 version 22.0.300 **Description** The issue is related to prototype pollution in the bitrix/templates/bitrix24/components/bitrix/menu/left vertical/script.js component of Bitrix24. This allows remote attackers to execute arbitrary JavaScript code in the victim's browser and possibly execute arbitrary PHP code on the server if the victim has administrator privileges. The exploitation is done by polluting ` proto [tag]` and ` proto [text]`. **Recommendations** For Bitrix24 version 22.0.300, consider disabling the script.js component temporarily until a patch is available to prevent exploitation. Restrict access to the bitrix/templates/bitrix24/components/bitrix/menu/left vertical/script.js file to minimize the risk of exploitation. Avoid using the ` proto [tag]` and ` proto [text]` variables in the affected component until the issue is resolved. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Bitrix24 version 22.0.300 **Description** A logic error in the `mb strpos()` function allows attackers to bypass XSS sanitization by placing HTML tags at the beginning of the payload, potentially leading to a cross-site scripting (XSS) attack. This issue is related to the failure to neutralize scripts in attributes on web pages. **Recommendations** For Bitrix24 version 22.0.300, consider disabling the `mb strpos()` function until a patch is available to prevent exploitation of this issue. Restrict access to any modules or functions that utilize the `mb strpos()` function to minimize the risk of XSS attacks. Avoid using HTML tags at the beginning of any payload in the affected version to reduce the risk of exploitation. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Bitrix24 versions prior to 22.0.300 **Description** An issue exists in the component `bitrix/modules/crm/lib/order/import/instagram.php` of Bitrix24 that stems from insufficient protection of web page structure. Exploitation of this issue could allow a remote attacker to execute arbitrary code by uploading a specially crafted ".htaccess" file. The issue allows for privilege escalation. The vulnerability is tracked as CVE-2023-1713. No information is available regarding the number of potentially affected devices worldwide or any real-world incidents where this issue has been exploited. The vulnerability involves insecure temporary file creation. The vulnerable file is located at `bitrix/modules/crm/lib/order/import/instagram.php`. **Recommendations** Disable or remove unused user accounts. Minimize user privileges. Utilize web application firewall (WAF) tools. Monitor server access logs for requests to '/upload/tmp/xxx/.htaccess' (where xxx is a 3-character alphanumeric string) or any request to '/upload/tmp/' via HTTP. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Obsidian desktop versions prior to 1.2.8 **Description** The issue is related to improper path handling, allowing a crafted webpage to access local files and exfiltrate them to remote web servers via "app://local/<absolute-path>". This can be exploited if a user opens a malicious markdown file in Obsidian or copies text from a malicious webpage and pastes it into Obsidian. **Recommendations** For versions prior to 1.2.8, update to version 1.2.8 or later to resolve the issue. As a temporary workaround, consider avoiding the use of the `app://local/<absolute-path>` protocol in Obsidian until a patch is applied. Additionally, users should be cautious when opening markdown files from untrusted sources or copying text from potentially malicious webpages.

**Name of the Vulnerable Software and Affected Versions** Typora versions prior to 1.6.7 **Description** The issue allows a crafted markdown file to run arbitrary JavaScript code in the context of Typora's main window via loading `typora://app/typemark/updater/update.html` in an `<embed>` tag. This can be exploited if a user opens a malicious markdown file in Typora or copies text from a malicious webpage and pastes it into Typora. **Recommendations** For versions prior to 1.6.7, update to version 1.6.7 or later to resolve the issue. As a temporary workaround, consider avoiding the use of the `<embed>` tag with `typora://app/typemark/updater/update.html` until a patch is applied. Additionally, users should be cautious when opening markdown files from untrusted sources or copying text from potentially malicious webpages.

**Name of the Vulnerable Software and Affected Versions** MarkText versions 0.17.1 and before **Description** The issue is a DOM-based XSS that allows arbitrary JavaScript code to run in the context of the MarkText main window. This can be exploited if a user copies text from a malicious webpage and pastes it into MarkText. The vulnerability is located in the src/muya/lib/contentState/pasteCtrl.js file. **Recommendations** For MarkText versions 0.17.1 and before, consider disabling the paste functionality in the `pasteCtrl.js` file as a temporary workaround until a patch is available. Restrict access to the `contentState` module to minimize the risk of exploitation. Avoid using the MarkText application to paste content from untrusted sources until the issue is resolved. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Typora versions prior to 1.7.0-dev **Description** The issue is related to improper path handling, which allows a crafted webpage to access local files and exfiltrate them to remote web servers via "typora://app/typemark/". This can be exploited if a user opens a malicious markdown file in Typora or copies text from a malicious webpage and pastes it into Typora. **Recommendations** For versions prior to 1.7.0-dev, update to version 1.7.0-dev or later to resolve the issue. As a temporary workaround, consider avoiding the use of the "typora://app/typemark/" endpoint until a patch is applied. Additionally, users should be cautious when opening markdown files from untrusted sources or copying text from potentially malicious webpages.

**Name of the Vulnerable Software and Affected Versions** Typora versions prior to 1.6.7 **Description** The issue is related to improper path handling, which allows a crafted webpage to access local files and exfiltrate them to remote web servers via "typora://app/<absolute-path>". This can be exploited if a user opens a malicious markdown file in Typora or copies text from a malicious webpage and pastes it into Typora. **Recommendations** For versions prior to 1.6.7, update to version 1.6.7 or later to resolve the issue. As a temporary workaround, consider avoiding the use of the "typora://app/<absolute-path>" protocol handler until a patch is applied. Additionally, users should be cautious when opening markdown files from untrusted sources or copying text from malicious webpages to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Triangle MicroWorks SCADA Data Gateway (affected versions not specified) **Description** This issue allows remote attackers to create arbitrary files on affected installations. User interaction is required, where the target must visit a malicious page or open a malicious file. The flaw exists within the processing of workspace files due to the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this to create files in the context of Administrator. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Proxmox Virtual Environment versions prior to 7.2-3 **Description** A reflected cross-site scripting (XSS) issue allows remote attackers to execute arbitrary web scripts or HTML via non-existent endpoints under the path "/api2/html/". This enables attackers to potentially manipulate web content. **Recommendations** For versions prior to 7.2-3, update to version 7.2-3 or later to resolve the issue. As a temporary workaround, consider restricting access to non-existent endpoints under the "/api2/html/" path to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Proxmox Virtual Environment (PVE) and Proxmox Mail Gateway (PMG) versions prior to pve-http-server 4.1-3 **Description** The issue affects Proxmox Virtual Environment (PVE) and Proxmox Mail Gateway (PMG) when proxying HTTP requests between pve(pmg)proxy and pve(pmg)daemon, allowing an attacker with an unprivileged account to craft an HTTP request and achieve Server-Side Request Forgery (SSRF) and file disclosure of any files on the server. Additionally, in Proxmox Mail Gateway, privilege escalation to the root@pam account is possible if the backup feature has been used, due to backup files having 0644 permissions and containing an authkey value. **Recommendations** For Proxmox Virtual Environment (PVE) and Proxmox Mail Gateway (PMG) versions prior to pve-http-server 4.1-3, update to pve-http-server 4.1-3 to fix the issue. As a temporary workaround, consider restricting access to the backup files and the `pve(pmg)proxy` and `pve(pmg)daemon` components to minimize the risk of exploitation. Avoid using the backup feature until the issue is resolved.