CVE-2017-15852
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 · uneditedInformation leak of the ISPIF base address in Android for MSM, Firefox OS for MSM, and QRD Android can occur in the camera driver.
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 confidenceAn information disclosure vulnerability in the camera driver exposes the ISPIF (Image Signal Processor Interface) base address to userspace. This leak could aid attackers in understanding memory layout and developing further exploits targeting the camera subsystem or related kernel components.
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 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.0/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.
-
Verify Android security patch levelCheck the device settings under Settings > About Phone > Security Patch Level. Compare the date to when the CVE was publicly disclosed (December 2017).Affected if The Security Patch Level is earlier than December 2017, indicating the device has not received the fix for this vulnerability.
-
Identify camera driver in useExamine /proc/config.gz (if available) or kernel configuration files for camera/ISP driver modules. Look for drivers related to ISPIF or image signal processing.Affected if The device uses a camera driver with ISPIF support and the kernel predates the December 2017 security updates.
-
Check for ISPIF memory exposureReview /dev or /sys/class/video4linux entries for camera devices. Attempt to read or map camera-related memory regions if accessible (requires root).Affected if Userspace processes can access ISPIF base address memory regions that should be restricted to kernel-only.
-
Audit camera subsystem permissionsCheck file permissions on /dev/video* devices and related camera driver nodes using ls -la. Verify which user/group can access them.Affected if Camera device nodes are accessible to unprivileged users or apps, increasing exposure to the information leak.
-
Review kernel logs for address exposureUse adb shell to run dmesg or check /proc/kmsg for any exposed kernel addresses related to ISPIF or camera subsystem.Affected if Kernel logs show ISPIF base addresses visible to userspace, indicating the vulnerability is present.
The device is affected if it runs an unpatched Google Android version with a camera driver that exposes ISPIF base address to userspace and has a pre-December-2017 security patch level.
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 security patches that address this camera driver information leak; update device firmware to the latest security patch level containing the fix for CVE-2017-15852.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15852 — 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-2017-15852 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