CVE-2022-33233
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 configuration weakness in modem wile sending command to write protected files.
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 memory corruption vulnerability exists in modem firmware due to a configuration weakness that improperly handles commands sent to write-protected files. The flaw allows memory corruption to occur when the modem processes write commands to protected file areas, likely due to insufficient access control or validation in the firmware's file handling subsystem.
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 chipset modelCheck the device documentation, system information, or run commands like 'at+qversion' (for Qualcomm modems) or 'lsusb'/'lspci' to identify the Qualcomm Apq chipset present in the systemAffected if The device uses any of the following chipsets: Apq8009, Apq8009w, Apq8017, Apq8037, Apq8052, Apq8056, Apq8076, or Apq8096au
-
Verify the firmware versionQuery the modem firmware version using AT commands such as 'at+qfirmware' or through the device's administrative interface under firmware or modem status sectionsAffected if The installed firmware version is any version of the affected Qualcomm Apq chipsets listed (all versions are affected)
-
Confirm administrative interface accessibilityCheck if the modem's configuration or administrative web interface is accessible on the network by attempting to access common ports (typically 80, 443, 8080) or using commands like 'netstat' to identify listening services related to modem managementAffected if The modem's configuration or administrative interface is exposed and accessible without restriction
-
Test for write command vulnerabilityIf administrative access is available, attempt to send a file write command (such as AT+QFSWRITE or similar file system write operations) to a protected file area and observe the response for successful execution or memory-related errorsAffected if Write commands to protected file areas execute without proper access control validation or trigger unexpected behavior indicating the vulnerability
The environment is affected if the device runs on any of the listed Qualcomm Apq chipsets (Apq8009, Apq8009w, Apq8017, Apq8037, Apq8052, Apq8056, Apq8076, Apq8096au) with any firmware version and the modem's file handling subsystem is accessible for write operations to protected areas.
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 vendor-provided patched versions; if unavailable, restrict administrative access to the modem's configuration interface and disable unnecessary remote management features to reduce attack surface.
- Consultation8.0 h
- Implementation16.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 $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33233 — 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-33233 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