CVE-2023-43511
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 · uneditedTransient DOS while parsing IPv6 extension header when WLAN firmware receives an IPv6 packet that contains `IPPROTO_NONE` as the next header.
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 denial of service vulnerability exists in WLAN firmware when parsing IPv6 extension headers. When the firmware processes an IPv6 packet containing IPPROTO_NONE (protocol 59, indicating 'no next header') in the next header field of an extension header, the parsing logic encounters an error causing a transient service disruption.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Qualcomm modem model in useCheck the device hardware specifications, boot logs, or modem interface (AT command responses for cellular modems) to determine if the device contains a Qualcomm 315 5g IoT, 9206 LTE, Apq8017, Apq8064au, Apq8092, Apq8094, Aqt1000, or Ar8031 componentAffected if The device contains any of the listed Qualcomm firmware components
-
Determine the firmware versionAccess the modem firmware information through vendor-specific interfaces (for example, AT+CGMR for cellular modems, or check the firmware image metadata) and compare the version string to the affected product listAffected if All versions of the listed Qualcomm firmware products are affected - if the firmware matches one of these products, it is vulnerable
-
Verify IPv6 support is enabledCheck the modem or device configuration for IPv6 protocol support settings. For cellular modems, verify PDP context or APN configuration includes IPv6 capabilityAffected if IPv6 must be enabled for the vulnerability to be exploitable - if IPv6 is disabled, the parsing code path is not triggered
-
Monitor for service disruption logsReview system or modem logs for unexpected resets, crash dumps, or denial of service indicators that coincide with IPv6 traffic processingAffected if Service disruptions occurring during IPv6 traffic processing may indicate the vulnerability has been triggered
The environment is affected if it contains any of the listed Qualcomm firmware products (all versions) with IPv6 support enabled, as the vulnerability triggers during IPv6 extension header parsing with IPPROTO_NONE.
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 firmware patches when available. As an interim measure, network-level filtering of IPv6 packets with IPPROTO_NONE in extension headers may block exploit attempts but could impact legitimate IPv6 traffic requiring careful testing.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43511 — 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-43511 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