Mock: privilege escalation for users that can access mock configuration
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions |
|---|---|---|---|
| n/a | mock | affected | — |
| Red Hat | Red Hat Enterprise Linux 6 | unaffected | — |
| Fedora | Extra Packages for Enterprise Linux | affected | — |
| Fedora | Fedora | affected | — |
Configuration 1 [-]
|
Configuration 2 [-]
|
No data.
No data available yet.
Vendor Workaround
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-0284 | The Mock software contains a vulnerability wherein an attacker could potentially exploit privilege escalation, enabling the execution of arbitrary code with root user privileges. This weakness stems from the absence of proper sandboxing during the expansion and execution of Jinja2 templates, which may be included in certain configuration parameters. While the Mock documentation advises treating users added to the mock group as privileged, certain build systems invoking mock on behalf of users might inadvertently permit less privileged users to define configuration tags. These tags could then be passed as parameters to mock during execution, potentially leading to the utilization of Jinja2 templates for remote privilege escalation and the execution of arbitrary code as the root user on the build server. |
Github GHSA |
GHSA-7j98-74jh-cjxh | Privilege escalation for users that can access mock configuration |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 1.6% (1.552% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-94 | |
| Metrics |
ssvc
|