CVE-2018-9361: This could lead to remote information disclosure with no additional execution privileges needed

Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available

What, why and how

In process_l2cap_cmd of l2c_main.cc, there is a possible out of bounds read due to a missing bounds check. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation. Product: Android Versions: Android-6.0 Android-6.0.1 Android-7.0 Android-7.1.1 Android-7.1.2 Android-8.0 Android-8.1 Android ID: A-74202041.

What

Why

The product reads data past the end, or before the beginning, of the intended buffer.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may obtain information outside the intended access boundary.

What

Why

The product reads data past the end, or before the beginning, of the intended buffer.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may obtain information outside the intended access boundary.

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path: a network path → Out-of-bounds Read → obtain information outside the intended access boundary
Attack surface: Network
Privileges required: None: unauthenticated exploitation is possible
User interaction: None
Attack complexity: Low: no specialised conditions are recorded
Security boundary: Unchanged: impact remains within the vulnerable component's security authority
Weakness ? CWE means Common Weakness Enumeration: a standard category for the underlying weakness.: CWE-125 ↗
CWE-125: Out-of-bounds Read. The product reads data past the end, or before the beginning, of the intended buffer.
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Common Vulnerability Scoring System 3.0: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land: No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.

NetworkUnauthenticatedCWE-125

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2018-20955Official EUVD mapping

0 linked advisory records.

Official EUVD record ↗

Canadian Centre for Cyber Security · English · AV18-094Android security bulletin

7-13077, CVE-2017-13227, CVE-2017-13230, CVE-2017-17558, CVE-2017-17806, CVE-2017-17807, CVE-2017-18155, CVE-2017-18156, CVE-2017-18157, CVE-2017-18158, CVE-2017-18158, CVE-2017-18159, CVE-2017-6290, CVE-2017-6292, CVE-2017-6294, CVE-2018-3569, CVE-2018-5146, CVE-2018-5829, CVE-2018-5830, CVE-2018-5831, CVE-2018-5834, CVE-2018-5835, CVE-2018-5854, CVE-2018-5884, CVE-2018-5885, CVE-2018-5891, CVE-2018-5892, CVE-2018-5894, CVE-2018-5896, CVE-2018-9339, CVE-2018-9340, CVE-2018-9341, CVE-2018-9344, CVE-2018-9345, CVE-2018-9346, CVE-2018-9347, CVE-2018-9348, CVE-2018-9355, CVE-2018-9356, CVE-2018-9357, CVE-2018-9358, CVE-2018-9359, CVE-2018-9360, CVE-2018-9361, CVE-2018-9362, CVE-2018-9363, CVE-2018-9364, CVE-2018-9366, CVE-2018-9367, CVE-2018-9368, CVE-2018-9369, CVE-2018-9370, CVE-2018-9371, CVE-2018-9372, CVE-2018-9373, CVE-2018-9409, CVE-2018-9338 Suggested Action CCIRC recommends that owner/operators test and deploy the vendor released updates to the affected platforms in accordance with their risk mitigation framework. References: https://source.android.com/security/bulletin/2018-06-01

Official advisory ↗

CERT-FR · French · CERTFR-2018-AVI-267Multiples vulnérabilités dans Google Android

.cve.org/CVERecord?id=CVE-2018-9346 Référence CVE CVE-2018-9347 https://www.cve.org/CVERecord?id=CVE-2018-9347 Référence CVE CVE-2018-9348 https://www.cve.org/CVERecord?id=CVE-2018-9348 Référence CVE CVE-2018-9355 https://www.cve.org/CVERecord?id=CVE-2018-9355 Référence CVE CVE-2018-9356 https://www.cve.org/CVERecord?id=CVE-2018-9356 Référence CVE CVE-2018-9357 https://www.cve.org/CVERecord?id=CVE-2018-9357 Référence CVE CVE-2018-9358 https://www.cve.org/CVERecord?id=CVE-2018-9358 Référence CVE CVE-2018-9359 https://www.cve.org/CVERecord?id=CVE-2018-9359 Référence CVE CVE-2018-9360 https://www.cve.org/CVERecord?id=CVE-2018-9360 Référence CVE CVE-2018-9361 https://www.cve.org/CVERecord?id=CVE-2018-9361 Référence CVE CVE-2018-9362 https://www.cve.org/CVERecord?id=CVE-2018-9362 Référence CVE CVE-2018-9363 https://www.cve.org/CVERecord?id=CVE-2018-9363 Référence CVE CVE-2018-9364 https://www.cve.org/CVERecord?id=CVE-2018-9364 Référence CVE CVE-2018-9366 https://www.cve.org/CVERecord?id=CVE-2018-9366 Référence CVE CVE-2018-9367 https://www.cve.org/CVERecord?id=CVE-2018-9367 Référence CVE CVE-2018-9368 https://www.cve.org/CVERecord?id=CVE-2018-9368 Référence CVE CVE-2018-9369 https://www.cve.org/CVERecord?id=CVE-2018-9369 Référence CVE CVE-2018-9370 https://www.cve.org/CVERecord?id=CVE-2018-9370 Ré

Official advisory ↗

JVN iPedia · Japanese · JVNDB-2018-011933Android における境界外読み取りに関する脆弱性

Android には、境界外読み取りに関する脆弱性が存在します。本脆弱性は、Android ID: A-74202041 として公開されています。

Official advisory ↗

Patch and workaround

Operational remediation based on structured source evidence.

Status ? Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.: Patch available
Affected: Android: Android-6.0 Android-6.0.1 Android-7.0 Android-7.1.1 Android-7.1.2 Android-8.0 Android-8.1
Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action: Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround: No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.

Evidence and provenance

Published 6 Nov 2018 · Last source change 16 Sept 2024, 16:18 UTC · CWE-125 · Out-of-bounds Read

CVE recordCVE.org · 5.1

CVSS sourceNIST NVD

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-09-01

European sourceENISA EUVD · EUVD-2018-20955

Product sourceCNA

Remediation sourceCVE/CNA references

CWE sourceNIST NVD

NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

16 Sept 2024, 16:18 UTC
Vendor guidanceAuthoritative vendor guidance changed from no authoritative guidance recorded to authoritative remediation link · patch.
Before
no authoritative guidance recorded
After
authoritative remediation link · patch
af854a3a-2127-422b-91ae-364da2661108 ↗
16 Sept 2024, 16:18 UTC
Affected versionsThe structured affected or fixed version information changed.
Before
Android-6.0 Android-6.0.1 Android-7.0 Android-7.1.1 Android-7.1.2 Android-8.0 Android-8.1 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
After
Android-6.0 Android-6.0.1 Android-7.0 Android-7.1.1 Android-7.1.2 Android-8.0 Android-8.1 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
CNA ↗
16 Sept 2024, 16:18 UTC
Remediation statusRemediation status changed from Awaiting fix to Patch available.
Before
Awaiting fix
After
Patch available
af854a3a-2127-422b-91ae-364da2661108 ↗
16 Sept 2024, 16:18 UTC
SeveritySeverity changed from Unknown to High.
Before
Unknown
After
High
NIST NVD ↗
16 Sept 2024, 16:18 UTC
CVSS scoreCVSS score changed from not recorded to 7.5 (CVSS 3.0 · NIST NVD · CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).
Before
not recorded
After
7.5 (CVSS 3.0 · NIST NVD · CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N)
NIST NVD ↗
1 Sept 2026, 02:42 UTC
ENISA EUVD mappingEUVD-2018-20955 was added to the official ENISA EUVD mapping for this CVE.
Before
not recorded
After
{"euvdId":"EUVD-2018-20955"}
ENISA EUVD ↗
16 Sept 2024, 16:18 UTC
Catalogue recordCVE added to the BlackTree catalogue.
CNA ↗

2018-11-06CVE published

2024-09-16Fixed release or patch reference recorded

ENISA EUVD · EUVD-2018-20955↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗

Technical terms and abbreviations used in this report

CVE: Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS: Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS: Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE: Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA: CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP: Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD: National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT: A computer security incident response team that publishes warnings or coordinates incident response.
PoC: Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF: Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL: Living off the land: abuse of legitimate tools or system functions during an attack.

This could lead to remote information disclosure with no additional execution privileges needed

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

ENISA European Vulnerability Database

EUVD-2018-20955

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

What changed after publication

This could lead to remote information disclosure with no additional execution privileges needed

National CERT insights ?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

EUVD-2018-20955

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.