dbcve.org
Qam8295p FirmwareOperating system · Qualcomm

CVE-2022-33274

HIGH · 7.8 CVSS v3.1 Published 2023-01-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Memory corruption in android core due to improper validation of array index while returning feature ids after license authentication.

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 confidence

A memory corruption vulnerability exists in Android core where improper validation of array indices occurs when returning feature IDs after license authentication. This could allow an authenticated attacker to trigger out-of-bounds memory access, potentially leading to arbitrary code execution or information disclosure.

MitigationApply the official Android security patch for CVE-2022-33274 which adds proper array index bounds checking in the license authentication feature ID retrieval code. Users should update their Android devices to the latest security patch level.

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 data
Qam8295p FirmwareOperating system
Affected:all versions
Qca6574au FirmwareOperating system
Affected:all versions
Qca6696 FirmwareOperating system
Affected:all versions
Sa6145p FirmwareOperating system
Affected:all versions
Sa6150p FirmwareOperating system
Affected:all versions
Sa6155p FirmwareOperating system
Affected:all versions
Sa8145p FirmwareOperating system
Affected:all versions
Sa8150p FirmwareOperating system
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Qualcomm firmware component
    Check the device firmware or system information to determine which Qualcomm component is present. On Android, this may be visible in /proc/cpuinfo, kernel logs, or vendor-specific system settings under 'About Phone' > 'Baseband version' or 'Modem version'.
    Affected if The device displays any of these firmware identifiers: Qam8295p, Qca6574au, Qca6696, Sa6145p, Sa6150p, Sa6155p, Sa8145p, or Sa8150p.
  2. Verify Android security patch level
    Navigate to Settings > About Phone > Android version or Security patch level on the Android device. Alternatively, run 'getprop ro.build.version.security_patch' via ADB shell.
    Affected if The security patch level is earlier than the August 2022 Android security update (or the specific patch date for CVE-2022-33274).
  3. Confirm license authentication feature is in use
    Review whether the device or application uses any license authentication functionality that retrieves feature IDs after authentication. Check application logs or system services that interact with the affected Qualcomm firmware component.
    Affected if The device actively uses the license authentication feature that retrieves feature IDs from the affected firmware component.
  4. Check for out-of-bounds memory access indicators
    Monitor system logs (logcat) or kernel logs for any error messages related to array index violations, memory access faults, or crashes occurring during or after license authentication operations.
    Affected if Any logs show memory access violations, crashes, or unexpected behavior related to the license authentication feature ID retrieval process.

The device is affected if it contains any of the listed Qualcomm firmware components AND uses the license authentication feature, and the Android security patch level predates the August 2022 update.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the official Android security patch for CVE-2022-33274 which adds proper array index bounds checking in the license authentication feature ID retrieval code. Users should update their Android devices to the latest security patch level.

Fix this in Qam8295p Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-33274 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-33274 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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