CVE-2021-1985
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 over read due to lack of data length check in QVR Service configuration in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Wearables
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 buffer over-read vulnerability exists in the QVR Service configuration parser due to insufficient data length validation. An attacker could potentially read beyond the bounds of allocated buffers by providing specially crafted configuration data, leading to information disclosure or potentially controlled memory content exposure.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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 chipset modelRetrieve the device or firmware model identifier using system information commands (e.g., 'getprop' on Android, or check /proc/cpuinfo, or review boot logs)Affected if The chipset model matches Apq8017, Apq8053, Apq8064au, Apq8096au, Aqt1000, Msm8917, Msm8953, or Msm8996au
-
Confirm QVR Service is presentSearch for the QVR Service binary or daemon in the firmware image or running processes (e.g., look for 'qvr', 'qvr_service', or similar process names in /proc or system service lists)Affected if The QVR Service executable or daemon exists on the system
-
Check if QVR configuration parser is enabledExamine QVR Service configuration files or settings that control the configuration parser functionalityAffected if Configuration parsing features are enabled or accessible to external input
-
Inspect QVR configuration data handlingReview configuration data files or inputs processed by the QVR Service to determine if length validation is performed before buffer operationsAffected if Configuration data can be supplied without proper bounds checking being observable in the code or configuration flow
The device is affected if it uses any of the listed Qualcomm chipset models (Apq8017, Apq8053, Apq8064au, Apq8096au, Aqt1000, Msm8917, Msm8953, Msm8996au) and has the QVR Service with its configuration parser enabled, since all firmware versions for these chipsets are vulnerable.
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 dataImplement bounds checking on all configuration data before buffer access operations in the QVR Service, ensuring data length is validated against buffer size prior to read operations.
- Consultation6.0 h
- Implementation8.0 h
- Testing16.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,792.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1985 — 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-2021-1985 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