CVE intelligence and bounded remediation
CVE-2023-6395 — Rpm-Software-Management Mock security vulnerability
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.
- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Published
- 2024-01-16
- CISA KEV
- Not currently listed
- Ecosystem
- software/application
- Weaknesses
- CWE-20, CWE-94
Affected products
- rpm-software-management / mock
- fedoraproject / extra_packages_for_enterprise_linux / 7.0
- fedoraproject / extra_packages_for_enterprise_linux / 8.0
- fedoraproject / extra_packages_for_enterprise_linux / 9.0
- fedoraproject / fedora / 38
- fedoraproject / fedora / 39
Matched remediation archetype
Command, code, expression, and template injection
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Trace untrusted values to process execution, interpreters, evaluators, template engines, dynamic imports, and administrative scripting features.
- Determine whether the affected path is reachable across each trust boundary and which service account or host privilege it inherits.
- Review configuration for optional execution features, unsafe compatibility modes, and shell invocation.
Remediate safely
- Replace string-built commands or evaluated code with fixed operations and structured argument APIs that do not invoke a shell.
- Use strict allowlists for operation identifiers and reject unexpected input before it reaches any interpreter.
- Update the affected component and add inert regression tests covering metacharacters, encoding variants, and alternate request paths.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.