dbcve.org
9205 Lte Modem FirmwareOperating system · Qualcomm

CVE-2023-33032

HIGH · 7.8 CVSS v3.1 Published 2024-01-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Memory corruption in TZ Secure OS while requesting a memory allocation from TA region.

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

Memory corruption vulnerability in TZ Secure OS occurring during memory allocation requests to the Trusted Application (TA) region. This could allow an attacker to corrupt memory or potentially execute arbitrary code within the secure environment.

MitigationApply vendor-provided security patches for TZ Secure OS; ensure memory allocation requests to TA regions include proper bounds checking and validation before memory is allocated.

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
9205 Lte Modem FirmwareOperating system
Affected:all versions
Aqt1000 FirmwareOperating system
Affected:all versions
Ar8031 FirmwareOperating system
Affected:all versions
C V2x 9150 FirmwareOperating system
Affected:all versions
Csr8811 FirmwareOperating system
Affected:all versions
Csra6620 FirmwareOperating system
Affected:all versions
Csra6640 FirmwareOperating system
Affected:all versions
Csrb31024 FirmwareOperating system
Affected:all versions

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

CVSS:3.1/AV:L/AC:L/PR:L/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. Identify Qualcomm firmware components in your environment
    Review hardware inventories, device firmware manifests, or baseband/modem version information to determine if any of these Qualcomm components are present: 9205 LTE Modem, Aqt1000, Ar8031, C V2X 9150, Csr8811, Csra6620, Csra6640, or Csrb31024
    Affected if Any of these eight specific Qualcomm firmware components are present in your environment (all versions are affected)
  2. Check device firmware or baseband version
    For consumer devices (phones, routers, IoT devices), access the device's baseband/modem firmware version through system information menus, AT command interfaces (for modems), or firmware metadata files
    Affected if The device firmware version corresponds to any of the affected Qualcomm products listed above
  3. Inspect system firmware for Qualcomm chipset identifiers
    Search system firmware images, bootloader components, or device documentation for strings or identifiers matching the affected product names (9205, Aqt1000, Ar8031, 9150, Csr8811, Csra6620, Csra6640, Csrb31024)
    Affected if These specific Qualcomm component identifiers are found in firmware or hardware documentation
  4. Verify TZ Secure OS is present
    Examine secure enclave, TrustZone, or TEE (Trusted Execution Environment) components in the device firmware to confirm TZ Secure OS is implemented
    Affected if TZ Secure OS is present and the device uses any of the affected Qualcomm firmware components

If your environment contains any of the eight listed Qualcomm firmware components (9205 LTE Modem, Aqt1000, Ar8031, C V2X 9150, Csr8811, Csra6620, Csra6640, or Csrb31024) with TZ Secure OS enabled, you are affected since all versions are vulnerable.

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

Apply vendor-provided security patches for TZ Secure OS; ensure memory allocation requests to TA regions include proper bounds checking and validation before memory is allocated.

Recommended fix Moderate confidence

Contact OEM for firmware containing Qualcomm CVE-2023-33032 patch ( Qualcomm typically issues patches to OEM customers; end users must obtain updated firmware from their device manufacturer)

  1. 1. Contact the device manufacturer (OEM/ODM) that uses the affected Qualcomm chipsets (9205 LTE Modem, Aqt1000, Ar8031, C V2x 9150, Csr8811, Csra6620, Csra6640, or Csrb31024)
  2. 2. Request the latest security patch from the manufacturer that addresses Qualcomm vulnerability CVE-2023-33032
  3. 3. Apply the manufacturer-provided firmware update that includes the Qualcomm security fix
  4. 4. Verify the TZ Secure OS has been updated by checking system information or contacting the manufacturer
Caveat Firmware updates may have compatibility considerations; test in controlled environment before production deployment

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

Fix this in 9205 Lte Modem Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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