dbcve.org
AltairApplication · Altairgraphql

CVE-2023-43799

HIGH · 7.8 CVSS v3.1 Published 2023-10-04
Fix available
A fix is available. Upgrade to 5.2.5 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
Altair is a GraphQL Client. Prior to version 5.2.5, the Altair GraphQL Client Desktop Application does not sanitize external URLs before passing them to the underlying system. Moreover, Altair GraphQL Client also does not isolate the context of the renderer process. This affects versions of the software running on MacOS, Windows, and Linux. Version 5.2.5 fixes this 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 · moderate confidence

The Altair GraphQL Client Desktop Application (versions prior to 5.2.5) fails to sanitize external URLs before passing them to the underlying operating system, and lacks proper renderer process isolation. This could allow malicious URLs to be processed by the system without validation, potentially enabling command injection or unauthorized system calls.

MitigationUpgrade Altair GraphQL Client to version 5.2.5 or later, which implements proper URL sanitization and renderer process isolation.

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
AltairApplication
Affected:< 5.2.5

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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. Identify installed Altair version
    Open the Altair GraphQL Client desktop application, then navigate to Help > About (or equivalent menu option) to view the installed version number
    Affected if The displayed version is lower than 5.2.5 (e.g., 5.2.4, 5.2.0, 5.1.x, etc.)
  2. Check application package metadata
    On Windows, open Programs and Features or check the installation directory for version information; on macOS, right-click the app and select Get Info; on Linux, check the package manager or application metadata
    Affected if The package or binary version listed is earlier than 5.2.5
  3. Verify URL handling behavior (if version is ambiguous)
    Attempt to open an external URL through the application (e.g., via a link in query results or documentation) and observe whether the system immediately passes it to the OS without any validation prompt
    Affected if External URLs are opened directly by the OS without sanitization warnings or confirmation dialogs, indicating the vulnerability may be present

You are affected if the installed Altair GraphQL Client version is earlier than 5.2.5 and the application processes external URLs without sanitization before passing them to the operating system.

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
Upgrade available Upgrade to 5.2.5 or later
Fixed in 5.2.5
Interim mitigation

Upgrade Altair GraphQL Client to version 5.2.5 or later, which implements proper URL sanitization and renderer process isolation.

Recommended fix High confidence

Upgrade to Altair GraphQL Client version 5.2.5

  1. 1. Check your current Altair version by opening the application and navigating to Help > About or checking the application menu
  2. 2. Download Altair GraphQL Client version 5.2.5 from the official GitHub releases page at github.com/altair-graphql/altair
  3. 3. Install the downloaded version, replacing your current installation
  4. 4. Verify the upgrade was successful by checking the version number in Help > About

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

Fix this in Altair Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-43799 — 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-2023-43799 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