Skip to content
Noroxi
CVE-2021-35113· NVD / CVE Program· CNA qualcomm

Possible authentication bypass due to improper order of signature verification and hashing in the signature verification call in Snapdragon

Possible authentication bypass due to improper order of signature verification and hashing in the signature verification call in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

MediumCVSS 6.8 · v3.1—No exploit No fix recorded

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help
Published
Sep 2, 2022
Updated
Jun 16, 2026
EPSS
0.1% · 3th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

27

Monitor

Low priority for now.

CVSS
27 / 40 · 6.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CNA vs NVD score

NVD
6.8
CNA · qualcomm
7.3
0.5 point gap

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
qualcommaqt1000 firmware
qualcommaqt1000
qualcommcsrb31024 firmware
qualcommcsrb31024
qualcommqca6174a firmware
qualcommqca6174a
qualcommqca6310 firmware
qualcommqca6310
qualcommqca6335 firmware
qualcommqca6335
qualcommqca6420 firmware
qualcommqca6420

and 84 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • qualcomm aqt1000 firmwareall versions
  • qualcomm csrb31024 firmwareall versions
  • qualcomm qca6174a firmwareall versions
  • qualcomm qca6310 firmwareall versions
  • qualcomm qca6335 firmwareall versions
  • qualcomm qca6420 firmwareall versions
  • qualcomm qca6430 firmwareall versions
  • qualcomm qca6564au firmwareall versions
  • qualcomm qca6574au firmwareall versions
  • qualcomm qca6595au firmwareall versions
  • qualcomm qca6696 firmwareall versions
  • qualcomm qca9377 firmwareall versions
  • qualcomm qcs410 firmwareall versions
  • qualcomm qcs610 firmwareall versions
  • qualcomm sa415m firmwareall versions
  • qualcomm sd 675 firmwareall versions
  • qualcomm sd429 firmwareall versions
  • qualcomm sd675 firmwareall versions
  • qualcomm sd678 firmwareall versions
  • qualcomm sd720g firmwareall versions

Versions reported by the vendor

Affected version ranges reported by the assigning authority (qualcomm). Independent of NVD's CPE analysis and usually ahead of it.

  • Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

    • AQT1000, CSRB31024, QCA6174A, QCA6310, QCA6335, QCA6420, QCA6430, QCA6564AU, QCA6574AU, QCA6595AU, QCA6696, QCA9377, QCS410, QCS610, SA415M, SD 675, SD429, SD675, SD678, SD720G, SD730, SD7c, SD845, SDaffected

Same product

qualcomm: all records

Other highest-scoring records for the same primary product.

  • CVE-2025-21479Incorrect Authorization in GraphicsKEV
    64This week
  • CVE-2025-21480Incorrect Authorization in Graphics WindowsKEV
    64This week
  • CVE-2021-1965Possible buffer overflow due to lack of parameter length check during MBSSID scan IE parse in Snapdragon Auto, Snapdragon Compute, Snapdrago
    40Plan
  • CVE-2023-43548Buffer Copy Without Checking Size of Input in Video
    39Monitor
  • CVE-2023-43519Buffer Copy without Checking Size of Input (`Classic Buffer Overflow`) in Video
    39Monitor
  • CVE-2023-43518Untrusted Pointer Dereference in Video
    39Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Physical access to the device is required.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Physical
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-347 · Improper Verification of Cryptographic Signature

CVSS vector

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

The verifier takes the algorithm to verify with from the token’s own header. Untrusted data ends up deciding its own verification rule.

The bug in code

The whole CWE-347 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const claims = jwt.verify(token, publicKey);

Fixed

ts
const claims = jwt.verify(token, publicKey, {  algorithms: ["RS256"],  issuer: "https://id.example.com",  audience: "portal",});

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records