CVE-2019-9248
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 · uneditedIn the Android kernel in the FingerTipS touchscreen driver there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.
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 confidenceIn the Android kernel's FingerTipS touchscreen driver, an out of bounds write vulnerability exists due to a missing bounds check. This allows a local attacker with System-level access to escalate privileges further by exploiting the missing boundary validation in the touchscreen driver 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 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 Android Security Patch LevelGo to Settings > About Phone > Build Number (or Settings > Security > Security Patch Level on some devices) and note the displayed date (e.g., February 2020, March 2020)Affected if The security patch level is earlier than the date when this CVE was addressed in the Android security bulletin (CVE-2019-9248 was addressed in the Android Security Patch Level of February 2020 or later)
-
Confirm the FingerTipS touchscreen driver is presentCheck /sys/class/input/ for touchscreen device entries or examine the kernel boot logs (dmesg | grep -i fingertips or dmesg | grep -i touchscreen) for FingerTipS driver loadingAffected if The device uses the FingerTipS touchscreen driver; the vulnerability only applies if this specific driver is loaded on the device
-
Verify System-level access existsReview user account permissions or check if any applications or processes hold SYSTEM-level privileges via 'ps -U system' or examining running services with uid 1000 (system)Affected if The attacker already has System-level access, which is required to exploit this vulnerability - the check determines if the privilege escalation path is relevant to the threat model
A device is affected if it uses the FingerTipS touchscreen driver and its Android Security Patch Level predates the February 2020 security update, allowing a System-level attacker to perform an out-of-bounds write for further privilege escalation.
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 Android security patch level that addresses this vulnerability in the FingerTipS driver; kernel and driver updates from the device OEM or Android security bulletin should be deployed.
- Consultation4.0 h
- Implementation8.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-9248 — 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-2019-9248 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