CVE-2022-33302
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 · uneditedMemory corruption due to improper validation of array index in User Identity Module when APN TLV length is greater than command length.
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 confidenceA memory corruption vulnerability exists in the User Identity Module (UIM) due to improper validation of array indices. When processing APN (Access Point Name) TLV (Type-Length-Value) data, the code fails to properly validate that the TLV length does not exceed the command length, allowing an attacker to trigger out-of-bounds memory access via manipulated array indexes.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the modem or chipset firmware modelQuery the baseband or modem subsystem for the firmware identifier using AT commands (e.g., AT+CGMM or manufacturer-specific diagnostics) or check the system firmware partitions for Qualcomm chipset identifiers such as '315', '9205', '9206', '9207', 'APQ8017', 'APQ8037', 'AQT1000', or 'AR6003'Affected if The detected model matches any of the listed affected firmware identifiers
-
Confirm the UIM module is activeCheck the modem or baseband subsystem status for the User Identity Module (UIM) component being loaded and operational. This may be visible in modem diagnostic logs, AT command responses (e.g., AT+CUIMINFO), or through manufacturer-specific firmware introspection toolsAffected if The UIM module is present and active in the firmware configuration
-
Verify APN handling is enabledInspect the modem or baseband configuration for Access Point Name (APN) settings and TLV processing functionality. Check APN-related configuration files, AT commands (e.g., AT+CGDCONT, AT+CGACT), or the UIM APN TLV handling code path if accessible through firmware debugging interfacesAffected if APN configuration and TLV processing are enabled in the UIM firmware
-
Review modem firmware version stringRetrieve the full firmware version string from the modem subsystem using AT commands (e.g., AT+CGMR or ATI) or by reading the firmware metadata from the baseband partition. Compare against the affected product list noting that all versions of each listed firmware are vulnerableAffected if The firmware version corresponds to any of the affected Qualcomm products regardless of version number
A system is affected if it runs any of the listed Qualcomm firmware products (315, 9205, 9206, 9207, APQ8017, APQ8037, AQT1000, AR6003) with the UIM module active and APN TLV processing enabled.
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 vendor-provided patches to the UIM firmware that implement proper bounds checking on APN TLV length against command length before array index calculations. Prioritize this high-severity patch in mobile device and baseband firmware update cycles.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33302 — 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-2022-33302 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