CVE-2022-33248
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 User Identity Module due to integer overflow to buffer overflow when a segement is received via qmi http.
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 confidenceMemory corruption vulnerability in the User Identity Module (UIM) of Qualcomm components. An integer overflow occurs when processing a received segment via QMI HTTP, leading to a buffer overflow that corrupts memory. The UIM handles SIM card communication, making this a critical baseband/firmware-level issue.
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 Qualcomm chipset model in the deviceConsult device documentation, FCC filing, or use AT commands (e.g., AT+CGMM or AT+GMM) to query the modem chipset model. On Linux-based devices, check /proc/cpuinfo or kernel boot logs for chip identification.Affected if The chipset model matches Apq8009, Apq8009w, Apq8017, Apq8037, Aqt1000, Ar8035, Csra6620, or Csra6640
-
Confirm the firmware versionQuery the baseband firmware version using AT commands such as AT+CGMR or AT+GMR. On Android devices, check Settings > About Phone > Baseband version. On Linux, use mmcli --modem or qmicli --device-open-proxy to query modem firmware info.Affected if The device runs any firmware version on the affected chipsets (all versions are vulnerable)
-
Verify UIM/SIM functionality is activeCheck if the device has an active SIM card and UIM module is initialized. Use AT+CPIN? to check SIM status, or on Linux check mmcli -L to list modems and their status. Look for UIM state in modem diagnostics.Affected if The device has an active SIM and UIM module is running (this is the vulnerable component)
-
Check if QMI HTTP service is enabledExamine whether QMI HTTP service is active on the device. On Linux, run qmicli --device-open-proxy --uim-get-card-status or check /dev/cdc-wdm* interfaces. Use AT+QCFG="usbscript" or similar vendor-specific commands to inspect QMI service configuration.Affected if QMI HTTP service is enabled and processing network-received segments (this is the attack vector)
The device is affected if it uses any of the listed Qualcomm chipsets (Apq8009, Apq8009w, Apq8017, Apq8037, Aqt1000, Ar8035, Csra6620, Csra6640) and has an active UIM with QMI HTTP service, since all firmware versions of these chips are vulnerable.
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-supplied firmware patches for the Qualcomm modem/baseband processor. Until patches are available, monitor for vendor security advisories and consider network segmentation to limit exposure of affected devices.
- Consultation4.0 h
- Implementation2.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 $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33248 — 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-33248 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