CVE-2024-54147
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 · uneditedAltair is a GraphQL client for all platforms. Prior to version 8.0.5, Altair GraphQL Client's desktop app does not validate HTTPS certificates allowing a man-in-the-middle to intercept all requests. Any Altair users on untrusted networks (eg. public wifi, malicious DNS servers) may have all GraphQL request and response headers and bodies fully compromised including authorization tokens. The attack also allows obtaining full access to any signed-in Altair GraphQL Cloud account and replacing payment checkout pages with a malicious website. Version 8.0.5 fixes the issue.
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 confidenceThe Altair GraphQL Client desktop application fails to validate HTTPS certificates, allowing man-in-the-middle attackers on untrusted networks to intercept all GraphQL traffic. This exposes request/response headers, bodies, and authorization tokens, while also enabling account takeover of Altair GraphQL Cloud and malicious replacement of payment pages.
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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/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.
-
Check installed Altair GraphQL Client versionOpen the desktop application and navigate to Help > About, or check the application executable properties to find the version numberAffected if The version is earlier than 8.0.5 (vulnerable versions lack proper HTTPS certificate validation)
-
Identify network traffic handling configurationReview the application's network settings or proxy configuration files for any settings that disable certificate verificationAffected if Certificate validation is explicitly disabled or bypassed in application settings
-
Test HTTPS certificate validation behaviorOn an untrusted network, use a network proxy (such as Burp Suite or mitmproxy) with an invalid certificate to attempt intercepting GraphQL traffic from AltairAffected if The application accepts the invalid certificate without warning or error, confirming certificate validation is not functioning
-
Verify GraphQL endpoint connectionsCheck the configured GraphQL endpoints in Altair - look for endpoints using HTTPS URLs in your saved requests or collectionsAffected if HTTPS endpoints are configured and the application connects to them without certificate validation errors despite network interception attempts
You are affected if your Altair GraphQL Client desktop version is earlier than 8.0.5 and the application accepts HTTPS connections without properly validating certificates, allowing intercepted traffic.
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.
dbcve · scopedUpdate Altair GraphQL Client to version 8.0.5 or later to enable proper HTTPS certificate validation.
Version 8.0.5
- Determine your current Altair GraphQL Client desktop version
- Download Altair GraphQL Client version 8.0.5 or later from the official source (github.com)
- Uninstall the current version if installing a fresh copy, or use the application's built-in update mechanism if available
- Install version 8.0.5
- Verify the installation shows version 8.0.5 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54147 — 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-54147 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