CVE-2018-9467
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 getHost() function of UriTest.java, there is the possibility of incorrect web origin determination. This could lead to incorrect security decisions with no additional 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 · moderate confidenceA vulnerability in the getHost() function of UriTest.java allows incorrect web origin determination, which could lead to incorrect security decisions being made without requiring any additional privileges or user interaction.
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 data= 7.0= 7.1.1= 7.1.2= 8.0= 8.1= 9.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Check Android OS versionGo to Settings > About Phone > Android version, or run 'adb shell getprop ro.build.version.release'Affected if The version is 7.0, 7.1.1, 7.1.2, 8.0, 8.1, or 9.0
-
Identify if app uses Uri.getHost() for security decisionsReview application code for calls to android.net.Uri.getHost() used in origin validation, permission checks, or WebView URL handlingAffected if The application relies on getHost() to determine web origins for security decisions
-
Test URI parsing edge casesConstruct URIs with unusual host formats (e.g., encoded characters, port in host field, IP addresses) and verify getHost() returns expected values according to RFC 3986Affected if getHost() returns unexpected or malformed host values for non-standard URIs
If the device runs Android 7.0 through 9.0 and uses Uri.getHost() for security-relevant origin determination, the environment is likely affected.
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.
dbcve · scopedFix the getHost() function to properly determine web origins according to RFC 3986 and relevant security specifications, ensuring correct URI parsing for security decisions.
- Apply the July 2018 Android Security Patch Level (SPL) or later to the affected device. This update contains the fix for the Uri.getHost() origin determination vulnerability in the Android Framework.
- Verify the device has received the update by checking Settings > System > Security > Security patch level - it should show 'July 2018' or a later date.
- For enterprise-managed devices, ensure your MDM/MEM solution is deploying the July 2018 Android security update to all enrolled devices running the affected Android versions.
- If OTA updates are unavailable, contact the device manufacturer for a patched build or consider device replacement with a model receiving regular security updates.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-9467 — 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-2018-9467 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