CVE-2022-33288
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 buffer copy without checking the size of input in Core while sending SCM command to get write protection information.
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 buffer overflow vulnerability exists in the Core component where a buffer copy operation does not validate the input size before copying data. When sending an SCM (Security Control Manager) command to retrieve write protection information, an attacker can provide oversized input that corrupts memory, potentially leading to code execution or denial of service.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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 firmware productCheck the system information or firmware version string on the device (e.g., via 'cat /proc/version', 'uname -a', or device-specific diagnostic interfaces). Look for product identifiers: 315 5g Iot Modem, Aqt1000, Ar8035, Wcn3998, Wcn6750, Qca6390, Wcn685x 5, or Wcn685x 1.Affected if The device runs any of the listed Qualcomm firmware products (315 5g Iot Modem, Aqt1000, Ar8035, Wcn3998, Wcn6750, Qca6390, Wcn685x 5, or Wcn685x 1)
-
Verify SCM subsystem is presentCheck if the Security Control Manager (SCM) subsystem is present and loaded on the firmware. This may be visible in firmware module listings, kernel config, or firmware debug interfaces. Look for SCM-related kernel modules, firmware blobs, or SCM daemon processes.Affected if The SCM subsystem is present in the firmware build
-
Confirm write protection command handler existsInspect firmware components or SCM command definitions for the write protection information retrieval functionality. Search for write protection related command handlers or APIs within the Core component. This may require firmware binary analysis or access to SCM command tables.Affected if The write protection information retrieval command handler is present in the SCM Core component
-
Check if vulnerable code path is reachableDetermine if the SCM command for write protection can be invoked from the device's attack surface. This may involve checking if there are interfaces (e.g., debug ports, diagnostic APIs, or exposed services) that allow sending SCM commands to the firmware.Affected if The device exposes any interface that allows sending SCM commands to the firmware
A device is affected if it runs any version of the listed Qualcomm firmware products (315 5g Iot Modem, Aqt1000, Ar8035, Wcn3998, Wcn6750, Qca6390, Wcn685x 5, or Wcn685x 1) and has the SCM subsystem with the write protection command handler present and reachable.
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 dataImplement proper input validation and bounds checking before buffer copy operations in the SCM command handler for write protection information. Validate input size against the destination buffer capacity.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33288 — 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-33288 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