CVE-2024-6861
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 · uneditedA disclosure of sensitive information flaw was found in foreman via the GraphQL API. If the introspection feature is enabled, it is possible for attackers to retrieve sensitive admin authentication keys which could result in a compromise of the entire product's API.
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 · moderate confidenceThe Foreman product's GraphQL API has an information disclosure vulnerability where the introspection feature, when enabled, exposes sensitive admin authentication keys to unauthenticated or low-privileged attackers. GraphQL introspection queries can retrieve schema details that inadvertently include or lead to exposure of credentials, allowing full API compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Foreman GraphQL endpoint is accessibleIdentify if your Foreman instance exposes a GraphQL API endpoint (typically at /api/graphql or /graphql). Try accessing it with a curl request: curl -s https://your-foreman-host/api/graphql -o /dev/null -w '%{http_code}'Affected if The endpoint returns HTTP 200, meaning GraphQL is active and potentially exposed
-
Verify GraphQL introspection is enabledSend an introspection query to the GraphQL endpoint to check if __schema is queryable. Example: curl -s -X POST https://your-foreman-host/api/graphql -H 'Content-Type: application/json' -d '{"query":"{__schema{types{name}}}"}'Affected if The response returns valid JSON with schema type information, indicating introspection is not disabled
-
Check if sensitive credentials appear in introspection resultsSearch the introspection query response for keywords indicating credentials: grep -iE '(key|token|secret|password|credential|auth)' response.jsonAffected if The introspection query response contains any authentication tokens, API keys, or credential-related fields accessible to the requester
-
Confirm authentication level required for introspectionTest the introspection query without authentication or with a low-privileged user account to see if schema details are returned without proper credentialsAffected if Unauthenticated or low-privileged users can retrieve schema details that should require admin-level access
You are affected if your Foreman GraphQL introspection is enabled and exposes authentication credentials or keys to unauthenticated or low-privileged users.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataDisable or restrict GraphQL introspection in production environments and implement proper authentication and role-based access controls on GraphQL endpoints to prevent unauthorized schema queries.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6861 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-6861 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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