CVE-2023-33076
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 Core when updating rollback version for TA and OTA feature is enabled.
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 confidenceMemory corruption vulnerability exists in the Core component when the system updates rollback versions for Trusted Applications (TA) with Over-The-Air (OTA) update features enabled. The vulnerability allows local attackers to potentially execute arbitrary code or cause denial of service through memory corruption during the rollback version update process.
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 and firmware versionCheck the device or system documentation to determine the exact Qualcomm chipset model (Aqt1000, Ar8035, Fastconnect 6200/6700/6800/6900/7800, or Qam8255p) and its current firmware version. This can typically be found in system information, modem diagnostics, or by querying the firmware directly via vendor-specific tools or AT commands.Affected if The device uses any of the listed affected chipsets (Aqt1000, Ar8035, Fastconnect 6200/6700/6800/6900/7800, or Qam8255p) with any firmware version.
-
Verify if OTA update feature is enabledInspect the system configuration or settings to determine whether Over-The-Air (OTA) update functionality is currently enabled. This may be found in firmware configuration files, device management settings, or through vendor-specific diagnostic interfaces.Affected if OTA update features are enabled in the system configuration.
-
Check if Trusted Applications (TA) are in useDetermine whether Trusted Applications are installed, configured, or active on the system. This can be verified through the trusted execution environment (TEE) management interface, TA inventory listings, or platform-specific security configuration tools provided by the vendor.Affected if Trusted Applications are present or configured on the system.
-
Review system logs for rollback update activityExamine system, kernel, or firmware logs for any entries related to Trusted Application rollback version updates or OTA rollback processes. Look for indicators such as TA version rollback, OTA update failures, or memory allocation events during the update cycle.Affected if Logs indicate recent or recurring TA rollback version updates occurring with OTA features active.
A system is likely affected if it runs any of the listed Qualcomm firmware versions (Aqt1000, Ar8035, Fastconnect series, or Qam8255p) with OTA update features enabled and has Trusted Applications configured, as the vulnerability requires all three conditions to be present.
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 addressing the memory corruption in Core when TA and OTA features are in use; if patches are unavailable, consider disabling OTA update features as a temporary workaround pending patch availability.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33076 — 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-2023-33076 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