Security readout for executives and security teams
Plain-English summary
This Android issue could cause software to misunderstand the true web origin of a URI. That can lead to wrong trust decisions, such as treating one origin as another. The public bundle names Android 6.0 through 8.1 and does not provide severity, CVSS, or active exploitation evidence.
Executive priority
Treat this as a legacy Android patch and lifecycle risk. It is not currently supported by evidence of active exploitation in the supplied sources, but origin confusion can affect authentication and trust boundaries.
Technical view
CVE-2017-13274 concerns incorrect web origin determination in Android’s getHost() behavior as described for UriTest.java. The impact is incorrect security decisions without additional execution privileges or user interaction. The provided sources list Android 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, and 8.1 as affected.
Likely exposure
Exposure is most likely in legacy Android fleets running versions 6.0 through 8.1, especially devices without the relevant Android security bulletin fixes. Current exposure cannot be determined from version alone because OEM patch levels vary.
Exploitation context
The source bundle says exploitation needs no user interaction and no additional privileges. It does not cite public exploit activity, and CISA KEV status is false, so active exploitation should not be assumed.
Researcher notes
Public details are sparse: no CVSS, CWE, exploit status, or code-level fix detail is included in the bundle. Analysis should stay anchored to Android version exposure and vendor bulletin validation rather than assuming exploitability in specific apps.
Mitigation direction
- Apply Android security updates associated with the April 2018 bulletin where available.
- Upgrade or retire Android 6.0 through 8.1 devices lacking OEM fixes.
- Check device OEM guidance for the exact patched build or security patch level.
- Prioritize managed devices handling sensitive web, SSO, or embedded browser workflows.
Validation and detection
- Inventory Android devices running versions 6.0, 6.0.1, 7.x, 8.0, or 8.1.
- Verify each device’s OEM build includes the relevant Android security bulletin fix.
- Confirm MDM compliance rules flag unsupported or unpatched Android builds.
- Review high-risk mobile workflows that depend on URI host or origin trust decisions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CVE-2017-13274 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://source.android.com/security/bulletin/2018-04-01CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.