CVE-2020-11291
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 · uneditedPossible buffer overflow while updating ikev2 parameters for delete payloads received during informational exchange due to lack of check of input validation for certain parameters received from the ePDG server in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile
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 confidenceBuffer overflow vulnerability in IKEv2 implementation when processing delete payloads from ePDG servers due to missing input validation on certain parameters. An unauthenticated remote attacker could potentially execute arbitrary code by sending specially crafted IKEv2 delete payloads during informational exchange.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the chipset modelCheck /proc/cpuinfo or use 'getprop ro.board.platform' or 'cat /sys/devices/soc0/soc_id' to identify the Qualcomm Snapdragon chipsetAffected if The chipset matches Apq8017, Apq8053, Aqt1000, Csrb31024, Msm8917, Msm8920, Msm8940, or Msm8953
-
Confirm IKEv2 daemon is runningCheck for IKEv2-related processes such as 'charon', 'strongswan', or vendor-specific IKE daemons using 'ps | grep -i ike' or check for the service via 'getprop | grep -i ikev2'Affected if An IKEv2 daemon or service is active on the device, indicating the vulnerability surface is present
-
Check for ePDG configurationLook for ePDG-related configuration files or properties: 'getprop | grep epdg' or check /system/etc or /vendor/etc for ipsec or ikev2 configuration filesAffected if ePDG (evolved Packet Data Gateway) configuration exists, meaning the device can connect to operator IKEv2 infrastructure where specially crafted delete payloads could be received
-
Verify firmware version stringCheck firmware/build version via 'getprop ro.build.version.release' or 'getprop ro.modem.build.id' to document the exact version for comparisonAffected if Firmware is present on any of the listed affected chipsets (all versions are impacted)
A device is affected if it uses any of the listed Qualcomm chipsets (Apq8017, Apq8053, Aqt1000, Csrb31024, Msm8917, Msm8920, Msm8940, Msm8953) and has IKEv2/ePDG functionality enabled for mobile operator connections.
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 firmware updates for affected Snapdragon devices. For mobile devices, coordinate with carrier patch deployment schedules.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11291 — 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-2020-11291 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