dbcve.org
SatelliteApplication · Redhat

CVE-2024-7923

CRITICAL · 9.8 CVSS v3.1 Published 2024-09-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An authentication bypass vulnerability has been identified in Pulpcore when deployed with Gunicorn versions prior to 22.0, due to the puppet-pulpcore 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) which are using Pulpcore version 3.0+ and could potentially enable unauthorized users to gain administrative access.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Authentication bypass in Pulpcore when deployed with Gunicorn <22.0 via puppet-pulpcore configuration. Apache mod_proxy fails to properly unset headers due to restrictions on underscores in HTTP headers, allowing attackers to authenticate using malformed headers and potentially gain administrative access to Satellite deployments.

MitigationUpgrade Gunicorn to version 22.0 or later and configure Apache mod_proxy to properly handle header unset operations to prevent underscore-based header injection attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SatelliteApplication
Affected:= 6.13= 6.14= 6.15

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Red Hat Satellite version
    Check the installed Satellite version using 'satellite-installer --version' or 'rpm -qa | grep satellite'
    Affected if The version is exactly 6.13, 6.14, or 6.15
  2. Confirm Pulpcore deployment
    Check if the system uses puppet-pulpcore configuration by examining the Puppet manifest files or running 'facter -p pulp' if Puppet is available
    Affected if Pulpcore is deployed via puppet-pulpcore configuration on the Satellite server
  3. Identify Gunicorn version
    Check the installed Gunicorn version using 'pip show gunicorn' or 'rpm -qa | grep gunicorn' if installed via system packages
    Affected if Gunicorn version is installed and is less than 22.0
  4. Verify Apache mod_proxy is in use
    Check if Apache with mod_proxy is configured as a reverse proxy in front of Pulpcore by inspecting Apache configuration files (typically in /etc/httpd/conf.d/ or /etc/apache2/sites-available/)
    Affected if Apache mod_proxy is configured as the reverse proxy for the Pulpcore application
  5. Inspect header handling configuration
    Review Apache mod_proxy configuration for ProxyErrorOverride, ProxyPass, and any ProxyPassReverseProxyHeader directives. Check if the configuration attempts to unset or filter incoming HTTP headers
    Affected if Apache mod_proxy configuration includes ProxyPass directives for Pulpcore but lacks proper header filtering to reject headers containing underscores

A user is affected if they run Red Hat Satellite 6.13, 6.14, or 6.15 with puppet-pulpcore deployed using Gunicorn version below 22.0 behind Apache mod_proxy with vulnerable header handling configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Gunicorn to version 22.0 or later and configure Apache mod_proxy to properly handle header unset operations to prevent underscore-based header injection attacks.

Recommended fix High confidence

Gunicorn 22.0+ (delivered via Red Hat Satellite 6.13.1+, 6.14.1+, or 6.15.1+ update channels)

  1. Update the Gunicorn package to version 22.0.0 or later in the Satellite deployment environment
  2. Verify the puppet-pulpcore configuration no longer uses vulnerable header handling
  3. Restart the Pulpcore services to apply the Gunicorn update
  4. Confirm authentication is properly enforced through standard authentication headers
  5. Test that legitimate admin access works correctly post-update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Satellite Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,670
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-7923 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-7923 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data