LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9467: In the getHost() function of UriTest.java, there is the possibility of incorrect web origin determination.

In 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.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2018-9467 is an Android issue where a URI host could be interpreted incorrectly, potentially causing wrong web-origin security decisions. The source rates it critical with no user interaction or privileges required. The bundle does not provide evidence of active exploitation.

Executive priority

Treat as high-priority for legacy Android fleets because the stated impact is critical and exploitation requires no privileges or interaction. Urgency depends on whether affected Android versions remain in use and whether patch status is provable.

Technical view

The issue is described in Android UriTest.java getHost(), involving incorrect web origin determination. The CVSS 3.1 vector is network reachable, low complexity, no privileges, no user interaction, unchanged scope, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is indicated for Google Android versions 7, 8, 8.1, 9, and nyc-mr1-dev/nyc-mr2-dev branches. The bundle does not identify non-Android products or downstream OEM status.

Exploitation context

The provided CVE record says exploitation needs no additional execution privileges and no user interaction. KEV is false, and the bundle provides no cited evidence of exploitation in the wild or public exploit availability.

Researcher notes

Evidence is sparse in the supplied bundle. The core concern is incorrect host or origin determination in Android URI handling, which can undermine security decisions. Do not assume affected OEMs, exploitability details, or fixes beyond cited Android guidance.

Mitigation direction

  • Review the Android September 2018 security bulletin for vendor guidance.
  • Prioritize patch verification for Android 7, 8, 8.1, and 9 assets.
  • Upgrade or retire devices stuck on unsupported Android builds.
  • Ask OEM or mobile-device-management vendors for patch status evidence.

Validation and detection

  • Inventory Android versions and security patch levels across managed devices.
  • Confirm affected versions are remediated according to vendor bulletin guidance.
  • Check whether custom builds include the Android Uri handling fix.
  • Document exceptions for unsupported or unverifiable devices.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-276: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-9467 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2018-9467Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleAndroid7, 8, 8.1, 9, nyc-mr1-dev, nyc-mr2-devunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-276 · source CWE mapping

Incorrect Default Permissions

Incorrect Default Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.