Vulnerabilities

A vulnerability was detected in cskefu up to 8.0.1. Impacted is the function Upload of the file com/cskefu/cc/controller/resource/MediaController.java of the component File Upload. The manipulation results in cross site scripting. The attack may be launched remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Mattermost Desktop App versions

Mattermost versions 10.11.x

A security vulnerability has been detected in cskefu up to 8.0.1. This issue affects some unknown processing of the file com/cskefu/cc/controller/resource/MediaController.java of the component Endpoint. The manipulation of the argument url leads to server-side request forgery. The attack may be initiated remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Mattermost versions 11.1.x

URL Redirection to Untrusted Site (&amp;#39;Open Redirect&amp;#39;) vulnerability in TR7 Cyber ​​Defense Inc. Web Application Firewall allows Phishing.This issue affects Web Application Firewall: from 4.30 through 16022026.<br /> <br /> NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

A security flaw has been discovered in tushar-2223 Hotel-Management-System up to bb1f3b3666124b888f1e4bcf51b6fba9fbb01d15. This affects an unknown part of the file /home.php of the component HTTP POST Request Handler. Performing a manipulation of the argument Name/Email results in sql injection. The attack can be initiated remotely. The exploit has been released to the public and may be used for attacks. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. The vendor was contacted early about this disclosure but did not respond in any way.

A weakness has been identified in JeecgBoot 3.9.1. This vulnerability affects the function importDocumentFromZip of the file org/jeecg/modules/airag/llm/controller/AiragKnowledgeController.java of the component Retrieval-Augmented Generation. Executing a manipulation can lead to deserialization. The attack can be launched remotely. Attacks of this nature are highly complex. It is stated that the exploitability is difficult. The project was informed of the problem early through an issue report but has not responded yet.

A vulnerability was identified in ZenTao up to 21.7.8. Affected by this issue is the function delete of the file editor/control.php of the component Committer. Such manipulation of the argument filePath leads to path traversal. Upgrading to version 21.7.9 can resolve this issue. The affected component should be upgraded.

Mattermost versions 11.1.x

Emails sent by pretix can utilize placeholders that will be filled with customer data. For example, when {name}<br /> is used in an email template, it will be replaced with the buyer&amp;#39;s <br /> name for the final email. This mechanism contained two security-relevant<br /> bugs:<br /> <br /> <br /> <br /> * <br /> It was possible to exfiltrate information about the pretix system through specially crafted placeholder names such as {{event.__init__.__code__.co_filename}}.<br /> This way, an attacker with the ability to control email templates <br /> (usually every user of the pretix backend) could retrieve sensitive <br /> information from the system configuration, including even database <br /> passwords or API keys. pretix does include mechanisms to prevent the usage of such <br /> malicious placeholders, however due to a mistake in the code, they were <br /> not fully effective for the email subject.<br /> <br /> <br /> <br /> <br /> * <br /> Placeholders in subjects and plain text bodies of emails were <br /> wrongfully evaluated twice. Therefore, if the first evaluation of a <br /> placeholder again contains a placeholder, this second placeholder was <br /> rendered. This allows the rendering of placeholders controlled by the <br /> ticket buyer, and therefore the exploitation of the first issue as a <br /> ticket buyer. Luckily, the only buyer-controlled placeholder available <br /> in pretix by default (that is not validated in a way that prevents the <br /> issue) is {invoice_company}, which is very unusual (but not<br /> impossible) to be contained in an email subject template. In addition <br /> to broadening the attack surface of the first issue, this could <br /> theoretically also leak information about an order to one of the <br /> attendees within that order. However, we also consider this scenario <br /> very unlikely under typical conditions.<br /> <br /> <br /> Out of caution, we recommend that you rotate all passwords and API keys contained in your pretix.cfg https://docs.pretix.eu/self-hosting/config/  file.

Emails sent by pretix can utilize placeholders that will be filled with customer data. For example, when {name}<br /> is used in an email template, it will be replaced with the buyer&amp;#39;s <br /> name for the final email. This mechanism contained a security-relevant bug:<br /> <br /> It was possible to exfiltrate information about the pretix system through specially crafted placeholder names such as {{event.__init__.__code__.co_filename}}.<br /> This way, an attacker with the ability to control email templates <br /> (usually every user of the pretix backend) could retrieve sensitive <br /> information from the system configuration, including even database <br /> passwords or API keys. pretix does include mechanisms to prevent the usage of such <br /> malicious placeholders, however due to a mistake in the code, they were <br /> not fully effective for this plugin.<br /> <br /> Out of caution, we recommend that you rotate all passwords and API keys contained in your pretix.cfg file.