vciy

CVE-2018-9420

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

In BnCameraService::onTransact of CameraService.cpp, there is a possible information disclosure due to uninitialized data

CVE-2018-94204 of 4 sources documented this
21

rank 21 = 0 + 14 + 0 + 7 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.00076  ·  without this subject the record ranks 21

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 5.5, from NVD  ·  without this subject the record ranks 7

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 21

How much of the world it touches

NVD CPE configurations

7 products in the CPE ranges  ·  without this subject the record ranks 14

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 21

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$2,320over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$2,320 = $4.99M incident cost x 0.6121449559255632 exposure x 0.00076 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.00076EPSSNOT IN KEVas of 2026-09-20
Severity5.5 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementscoring model changedreceipt
PLATEAU10Minimal movement since 2024-11-20, 572 days at 0.00, as of 2026-06-15. arc-rules@v1

Foresight · where to check next

Google AndroidLinuxMicrosoft WindowsNetScaler ADC9420

This record is one instance of CWE-908, use of uninitialized resource. The index holds 897 prior instances of this class, 4 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signalspoke length is how much of the record matches, not how bad it is

Running Google Android? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachneeds local access · low privileges required · no user interaction · low attack complexityreceipt
ImpactComplete confidentiality lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classCWE-908 Use of Uninitialized Resourcereceipt
Published consequencesCWE-908: Confidentiality: Read Memory, Read Application Data; Availability: DoS: Crash, Exit, or Restart[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed inNo fix version in held sources, as the index stood on 15 Jun 2026.
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, NVD5.5 MEDIUMreceipt
Exploit probability0.00076 · top 100% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned bygoogle_androidreceipt
Recorded changes19 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productGoogle Androidreceipt
Published rangesgoogle android 6.0; google android 6.0.1; google android 7.0; google android 7.1.1receipt
Show all 7 published ranges
google android 6.0
google android 6.0.1
google android 7.0
google android 7.1.1
google android 7.1.2
google android 8.0
google android 8.1

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

In BnCameraService::onTransact of CameraService.cpp, there is a possible information disclosure due to uninitialized data. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation. receipt

NVD's analysis a second authority

severity
5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
weakness
CWE-908
affected versions
google android 6.0; google android 6.0.1; google android 7.0; and 4 more, listed in full below
also scored by
5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

check it yourself source.android.com receipt

Movement the material steps

20 Nov 20240.00043
17 Mar 20256e-05 · scoring model v2025.03.14
15 Jun 20260.00076 · scoring model v2026.06.15
Show all 19 observations
20 Nov 20240.00043
17 Mar 20256e-05
19 Mar 20257e-05
21 Mar 20259e-05
29 Mar 20250.00017
30 Mar 20259e-05
17 Apr 20257e-05
29 Apr 20258e-05
15 Jun 20259e-05
25 Jul 20250.0001
5 Aug 20250.00012
15 Aug 20250.00011
15 Sep 20250.00012
18 Nov 20250.00016
21 Nov 20250.00012
28 Dec 20250.00031
29 Dec 20250.00054
1 Jan 20260.00041
15 Jun 20260.00076

19 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.00076Published2024-11-19Index as of2026-06-15

The record had been public for 1 year, 6 months when this index was last written.

Published 2024-11-19 receipt · Index as of 2026-06-15 derived

The pattern, elsewhere

This record is one instance of CWE-908, use of uninitialized resource. The index holds 897 prior instances of this class, 4 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2024-29745 · Google Androidmatches 9 of 9KEV listed · 2024receipt
CVE-2024-50302 · Linuxmatches 8 of 9KEV listed · 2024receipt
CVE-2026-85880 · Microsoft Windows 10 Version 1607matches 6 of 9KEV listed · 2026receipt
CVE-2025-5777 · NetScaler ADConly 1 attribute comparableKEV listed · 2025receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

897 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Its defect family

google android

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: computed, pro@dim2000

Nothing we hold separates this record from the others in its defect family. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

These are index-wide views, not findings about CVE-2018-9420.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.