CVE-2020-11129
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 · uneditedu'During the error occurrence in capture request, the buffer is freed and later accessed causing the camera APP to fail due to memory use-after-free' in Snapdragon Consumer IOT, Snapdragon Mobile in Bitra, Kamorta, QCS605, Saipan, SDM710, SM8250, SXR2130
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 use-after-free vulnerability exists in the camera application of affected Snapdragon chipsets. During error handling in a capture request, a buffer is freed but subsequently accessed, leading to memory corruption. This could allow a local attacker to cause a denial of service or potentially execute arbitrary code.
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 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 Snapdragon chipset modelQuery the device or system information to determine the chipset model (e.g., via 'getprop' on Android, or system info utilities). Look for model identifiers: Bitra, Kamorta, QCS605, Saipan, SDM710, SM8250, or SXR2130.Affected if The chipset model matches one of the affected models: Bitra, Kamorta, QCS605, Saipan, SDM710, SM8250, or SXR2130.
-
Check the firmware versionRetrieve the firmware version for the identified chipset. On Android devices, this may be available via 'getprop' commands or in the device's system firmware directories. Since all versions are affected, any firmware version present indicates potential exposure.Affected if Any firmware version is installed on one of the affected chipset models.
-
Determine if camera application is enabledInspect whether the camera application or camera service is active on the device. Check camera daemon processes (e.g., camera provider service) and verify camera hardware is initialized or accessible.Affected if Camera functionality is enabled or the camera service is running on the affected firmware.
-
Verify camera capture request paths are usedReview if the device has performed any camera capture operations. Check camera usage logs or monitoring if camera functionality has been invoked since the vulnerability triggers during error handling in capture requests.Affected if Camera capture requests have been processed on the affected camera application firmware.
A user is affected if their device utilizes a Snapdragon chipset from the affected list (Bitra, Kamorta, QCS605, Saipan, SDM710, SM8250, SXR2130) with camera functionality enabled, as the use-after-free vulnerability exists in the camera application's capture request error handling.
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 the vendor-provided patch/firmware update from Qualcomm for the affected Snapdragon components (Bitra, Kamorta, QCS605, Saipan, SDM710, SM8250, SXR2130). Review camera capture code paths to ensure proper buffer lifecycle management.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11129 — 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-11129 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