CVE-2023-43529
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 processing IKEv2 Informational request messages, when a malformed fragment packet is received.
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 confidenceA vulnerability in IKEv2 (Internet Key Exchange v2) implementations allows an unauthenticated remote attacker to cause a denial of service by sending malformed fragment packets within IKEv2 Informational request messages. The processing of these specially crafted packets triggers the transient DOS condition.
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 firmware productCheck the device or system information to determine if it uses one of the affected products: Qualcomm 315 5g Iot Modem, Aqt1000, Ar8035, Csra6620, Csra6640, Csrb31024, Fastconnect 6200, or Fastconnect 6700 firmware. This may be visible in device specifications, boot logs, or network interface details.Affected if The system runs any of the listed Qualcomm firmware products (all versions are affected)
-
Determine if IKEv2 is enabledCheck the system configuration for IKEv2 (Internet Key Exchange v2) settings. On network devices, look for IKEv2 profiles, policies, or crypto configurations that enable IKEv2. On Linux systems, check for IKE daemon processes (like charon, strongswan) or IKE-related kernel modules.Affected if IKEv2 is actively configured or running on the system
-
Verify IKEv2 port exposureCheck if UDP ports 500 and/or 4500 (standard IKEv2 ports) are open and listening on the system using commands like 'netstat -anp' or 'ss -tulnp'. Also check firewall rules to confirm the system can receive IKEv2 traffic from the network.Affected if The IKEv2 ports are exposed to untrusted networks (UDP 500/4500)
-
Review IKEv2 fragment handlingExamine any available IKEv2 debug logs, packet captures, or system logs for evidence of malformed IKEv2 fragment packets or Informational request messages. Check if the system has logged any IKE parsing errors or unusual IKE message failures.Affected if Malformed IKEv2 fragment packets are being processed or causing errors
A system is affected if it runs any version of the listed Qualcomm firmware products with IKEv2 enabled and exposed to network traffic, as all versions of these products contain the vulnerability in IKEv2 fragment packet processing.
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-specific patches for IKEv2 implementations. If no patch is available, consider implementing network-level filtering to drop obviously malformed IKEv2 fragment packets at the perimeter, though this may not fully mitigate the vulnerability.
- Consultation2.0 h
- Implementation4.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 $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43529 — 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-43529 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