Mock Jinja2 Template input validation

Summaryinfo

A vulnerability was found in Mock and classified as critical. The affected element is an unknown function of the component Jinja2 Template Handler. Executing a manipulation can lead to input validation. This vulnerability appears as CVE-2023-6395. The attack requires local access. There is no available exploit.

Detailsinfo

A vulnerability was found in Mock (the affected version is unknown). It has been declared as critical. This vulnerability affects an unknown code of the component Jinja2 Template Handler. The manipulation with an unknown input leads to a input validation vulnerability. The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

There is a flaw in the Mock software where an attacker may achieve privilege escalation and execute arbitrary code as the root user. This is due to the lack of sandboxing when expanding and executing Jinja2 templates that may be included in some configuration parameters. Mock documentation recommends that users added to the mock group on a system be treated as privileged users. However, some build systems that invoke mock on behalf of users may unintentionally allow less privileged users to define configuration tags that will be passed to mock as parameters when run. Configuration tags that allow Jinja2 templates could be used to achieve remote privilege escalation and run arbitrary code as root on the build server.

The weakness was presented 01/16/2024. The advisory is shared for download at access.redhat.com. This vulnerability was named CVE-2023-6395 since 11/30/2023. There are neither technical details nor an exploit publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 261532 (Amazon Linux 2 : mock, --advisory ALAS2MOCK-2025-001 (ALASMOCK-2025-001)), which helps to determine the existence of the flaw in a target environment.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at Tenable (261532). Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• Mock

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion