dbcve.org
Ar8035 FirmwareOperating system · Qualcomm

CVE-2023-33103

HIGH · 7.5 CVSS v3.1 Published 2024-03-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Transient DOS while processing CAG info IE received from NW.

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 confidence

A denial-of-service vulnerability exists in how the device processes the Closed Access Group (CAG) information element received from the network. A specially crafted or malformed CAG info IE can trigger a transient DoS condition, potentially causing service disruption for affected users or devices.

MitigationApply vendor-provided security patches for this vulnerability. If no patch is available, consider network-level filtering or monitoring of CAG-related signaling to detect anomalous IE content.

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
Ar8035 FirmwareOperating system
Affected:all versions
Fastconnect 6700 FirmwareOperating system
Affected:all versions
Fastconnect 6900 FirmwareOperating system
Affected:all versions
Fastconnect 7800 FirmwareOperating system
Affected:all versions
Qca6174a FirmwareOperating system
Affected:all versions
Qca6584au FirmwareOperating system
Affected:all versions
Qca6698aq FirmwareOperating system
Affected:all versions
Qca8081 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 the Qualcomm wireless component
    Check system logs, hardware specifications, or network adapter details to determine if a Qualcomm Wi-Fi or cellular firmware component is in use. On Linux, check 'lspci -v' or 'iw list'; on Android, check 'Settings > About Phone > Baseband' or use 'getprop' commands.
    Affected if The system uses any of the following: Ar8035, Fastconnect 6700/6900/7800, Qca6174a, Qca6584au, Qca6698aq, or Qca8081 firmware.
  2. Determine the firmware version
    Retrieve the installed firmware version from the wireless adapter or system. On Linux: 'cat /sys/class/net/*/device/firmware_version' or check vendor-specific paths. On Android: 'getprop ro.build.fingerprint' or check 'Settings > Software Info > Build Number'.
    Affected if The firmware version is present and corresponds to any of the affected Qualcomm components listed.
  3. Check if CAG (Closed Access Group) feature is enabled
    Examine the wireless device configuration or network settings for CAG/Closed Access Group settings. In enterprise or carrier Wi-Fi contexts, check if the device is configured to connect to networks that use CAG IE. On managed devices, review group policy or profile settings.
    Affected if The device has CAG feature enabled or is configured to process CAG Information Elements from the network.
  4. Monitor for service disruption correlating with CAG IE receipt
    Capture wireless traffic or review system/network logs for errors, disconnects, or crashes occurring when the device connects to or roams between networks. Look for entries mentioning 'CAG', 'Closed Access Group', or 'IE processing' failures.
    Affected if The device experiences transient DoS symptoms (disconnects, crashes, service disruption) when connecting to networks that send CAG Information Elements.

The system is likely affected if it uses any of the listed Qualcomm firmware components (Ar8035, Fastconnect series, Qca series) with CAG feature enabled, and experiences DoS symptoms correlating with CAG IE processing.

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 vendor-provided security patches for this vulnerability. If no patch is available, consider network-level filtering or monitoring of CAG-related signaling to detect anomalous IE content.

Fix this in Ar8035 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-33103 — 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-2023-33103 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