CVE-2023-33054
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 · uneditedCryptographic issue in GPS HLOS Driver while downloading Qualcomm GNSS assistance data.
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 confidenceA cryptographic vulnerability exists in the GPS HLOS (High-Level Operating System) Driver during the download process of Qualcomm GNSS (Global Navigation Satellite System) assistance data. The CVSS 9.1 score indicates a critical, likely network-exploitable issue that could allow attackers to compromise the integrity or confidentiality of GPS assistance data, potentially enabling position spoofing or other attacks on location-dependent systems.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.
-
Identify affected Qualcomm chipsetQuery device/system inventory or firmware to identify if one of the following chips is present: Qualcomm 315 5G IoT Modem, Aqt1000, Ar8035, Csra6620, Csra6640, Wcn3991, Wcn3998, or Wcn6750. On Linux-based systems, use lspci, lsusb, or check /proc/device-tree/. For modems, AT commands may reveal chipset info.Affected if Any of the eight listed Qualcomm chipsets are present in the system
-
Verify GPS/GNSS functionality is enabledCheck whether the GNSS (GPS) subsystem is active on the device. Look for gnss-related kernel modules (lsmod | grep gnss), GPS daemons or services, or GPS hardware status in system diagnostics.Affected if GPS/GNSS functionality is enabled and the HLOS driver is loaded
-
Confirm assistance data download is enabledInspect GPS/GNSS configuration settings, service parameters, or network settings to determine if Assisted GNSS (A-GNSS) or assistance data download over the network is enabled. This is typically configured in modem settings, location services, or carrier provisioning.Affected if Assistance data download feature is enabled, as this is the code path where the vulnerability triggers
-
Check firmware version if accessibleIf firmware version information is accessible via diagnostic tools, AT commands for modems, or firmware metadata, retrieve it to compare against the affected version ranges. All versions listed as affected.Affected if Firmware version cannot be determined as patched or falls within an unpatched release
The system is affected if it contains any of the eight listed Qualcomm chipsets with GPS/GNSS enabled and assistance data download functionality active.
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 dataApply available vendor firmware/Software updates for affected Qualcomm components. Review and validate cryptographic implementations in GPS assistance data download pathways.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33054 — 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-2023-33054 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