# CVE-2024-7012: Puppet-foreman: an authentication bypass vulnerability exists in foreman

> Attackers can bypass authentication via malformed headers in Foreman with External Authentication, gaining administrative access to Red Hat Satellite deployments.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Sep 2024
- **Updated:** 11 Nov 2025
- **Also known as:** GHSA-gp3v-m4q9-3v8h

## What is CVE-2024-7012?

CVE-2024-7012 is a critical authentication bypass vulnerability in Redhat Satellite, published on 4 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An authentication bypass vulnerability has been identified in Foreman when deployed with External Authentication, due to the puppet-foreman configuration. This issue arises from Apache's mod_proxy not properly unsetting headers because of restrictions on underscores in HTTP headers, allowing authentication through a malformed header. This flaw impacts all active Satellite deployments (6.13, 6.14 and 6.15) and could potentially enable unauthorized users to gain administrative access.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2024-7012?

It affects 1 product.


Products: Redhat Satellite.

## How do I fix CVE-2024-7012?

Apply the vendor's patch.

## Is CVE-2024-7012 being exploited?

There is no known exploitation of CVE-2024-7012 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Satellite

- [CVE-2024-7923](https://insights.sbomify.com/CVE-2024-7923/): Puppet-pulpcore: an authentication bypass vulnerability exists in pulpcore (critical 9.8)
- [CVE-2026-96659](https://insights.sbomify.com/CVE-2026-96659/): Foreman: excessive permissions for viewer role on preview (critical 9.1)
- [CVE-2023-0118](https://insights.sbomify.com/CVE-2023-0118/): Foreman: arbitrary code execution through templates (critical 9.1)
- [CVE-2008-2369](https://insights.sbomify.com/CVE-2008-2369/): Hardcoded credentials in n/a (critical 9.1)
- [CVE-2026-96658](https://insights.sbomify.com/CVE-2026-96658/): Foreman: foreman: arbitrary code execution via safemode sandbox bypass (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-7012 and fix it if it is affected.

What it is: CVE-2024-7012 is a critical authentication bypass vulnerability in Redhat Satellite, published on 4 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-7012 in the wild and no public exploit code.

Affected product: Redhat Satellite. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-7012/ (Markdown: https://insights.sbomify.com/CVE-2024-7012/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-7012
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-7012
- OSV: https://osv.dev/vulnerability/CVE-2024-7012

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-7012/
Summaries are generated and may contain mistakes; the official description above is the record.