CVE-2014-7919
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 · uneditedb/libs/gui/ISurfaceComposer.cpp in Android allows attackers to trigger a denial of service (null pointer dereference and process crash).
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 null pointer dereference vulnerability exists in Android's ISurfaceComposer.cpp within the libs/gui graphics library. The vulnerability allows remote or local attackers to trigger a denial of service by causing the affected process to crash via the null pointer dereference.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/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.
-
Confirm the Android operating system is in useCheck the system properties or /system/build.prop file for the 'ro.build.version.release' property to verify the device is running AndroidAffected if The device is running any Android version (all versions are affected)
-
Identify the SurfaceFlinger service availabilityCheck if the SurfaceFlinger service (com.android.services.surfaceflinger) is accessible on the device by examining running processes via 'ps -A | grep surfaceflinger' or checking /sys/class/misc/android_surfaceflingerAffected if The SurfaceFlinger service is running, which provides the vulnerable ISurfaceComposer interface
-
Verify the libs/gui library is presentCheck for the existence of libgui.so in /system/lib/ or /vendor/lib/ directoriesAffected if The libgui.so library exists, which contains the vulnerable ISurfaceComposer.cpp code
-
Check for processes using the ISurfaceComposer interfaceLook for processes that communicate with SurfaceFlinger, such as SystemServer, SurfaceFlinger itself, or any app using SurfaceClient connectionsAffected if Any process communicates with the SurfaceFlinger service via the ISurfaceComposer AIDL interface
-
Assess graphic buffer allocation capabilityTest whether the device can create and manipulate graphic buffers through SurfaceComposerClient by examining logcat for errors during surface creation or buffer allocationAffected if Graphic buffer allocation via SurfaceComposerClient succeeds, indicating the vulnerable code path is accessible
Since all Android versions are affected, the device is vulnerable if it runs Android and has the SurfaceFlinger/ISurfaceComposer graphics subsystem active, which is standard on all Android devices.
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 relevant Android system security updates/patches. As this is a system library issue in the Android framework, remediation requires updating the device to a patched Android version.
- Consultation2.0 h
- Testing3.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 $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-7919 — 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-2014-7919 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