CVE-2022-33264
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 in modem due to stack based buffer overflow while parsing OTASP Key Generation Request Message.
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 confidenceStack-based buffer overflow in the modem's OTASP Key Generation Request Message parser causes memory corruption. The vulnerability stems from insufficient bounds checking during parsing of the OTASP message, allowing an attacker to overwrite stack memory and potentially achieve code execution in the modem context.
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 firmware modelQuery the modem or check system documentation for the exact firmware name and version (for example, using AT commands like AT+CGMR or checking the bootloader/binary firmware headers)Affected if The firmware model matches one of the affected products: Qualcomm 315 5g Iot, 9207 Lte, Apq8017, Apq8037, Aqt1000, Ar6003, Ar8035, or C V2x 9150
-
Confirm OTASP feature is enabledCheck the modem configuration for OTASP (Over-The-Air Service Provisioning) settings, typically found in the modem's provisioning, service provisioning, or network configuration filesAffected if OTASP functionality is present and enabled on the modem
-
Inspect OTASP message handler configurationExamine the modem's OTASP Key Generation Request Message parser configuration or related provisioning scripts for any evidence of custom input validation or bounds checkingAffected if The OTASP parser relies on the default firmware implementation without additional input validation layers
If the deployed modem runs one of the listed Qualcomm firmware variants with OTASP provisioning enabled and no custom input validation is applied to OTASP message parsing, the environment is likely affected by this stack-based buffer overflow.
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 dataUpdate modem firmware to a version containing the patched bounds checking logic for OTASP message parsing; if firmware updates are unavailable, implement input validation and length checks before parsing OTASP messages.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33264 — 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-33264 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