LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9379: In multiple functions of MiniThumbFile.java, there is a possible way to view the thumbnails of deleted phot...

In multiple functions of MiniThumbFile.java, there is a possible way to view the thumbnails of deleted photos due to a confused deputy. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

MediumCVSS 5.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Android flaw could let a local low-privileged actor view thumbnails of photos that a user deleted. The business impact is privacy exposure, not device takeover. Sources do not show active exploitation or a public exploit.

Executive priority

Handle through mobile patch compliance rather than emergency response. Prioritize devices used with sensitive photos, regulated data, or unmanaged BYOD access.

Technical view

CVE-2018-9379 is an information disclosure issue in MiniThumbFile.java caused by confused-deputy behavior. The CVSS vector is local, low complexity, low privileges, no user interaction, unchanged scope, and high confidentiality impact only.

Likely exposure

Exposure appears limited to affected Android devices where an attacker or app already has local low-privileged access. The provided affected-product data is sparse and should be validated against Android or device-vendor patch guidance.

Exploitation context

The source bundle states exploitation requires local access with low privileges and no user interaction. CISA KEV status is false, and no cited source in the bundle reports active exploitation.

Researcher notes

Evidence supports local information disclosure of deleted-photo thumbnails. The bundle does not provide exploit details, affected Android version ranges, or named mitigations beyond the referenced Pixel bulletin. Avoid assuming kernel-only scope despite the affected metadata label.

Mitigation direction

  • Confirm affected Android devices have the relevant June 2018 or later vendor security update.
  • Check Google Pixel or OEM guidance for exact affected builds and patch levels.
  • Retire or restrict unsupported Android devices that cannot receive security updates.
  • Limit corporate data exposure on unmanaged or personally owned Android devices.

Validation and detection

  • Inventory Android device models, OS versions, and security patch levels.
  • Compare patch levels against the referenced Pixel June 2018 bulletin and OEM advisories.
  • Review MDM compliance reports for devices below required Android security patch levels.
  • Treat missing vendor patch data as unresolved exposure until confirmed.
Prepared
Confidence
medium
Sources
3

Public sources used

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 · medium confidence lookup

CWE-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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-9379 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
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

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

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
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N1.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2018-9379Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleAndroidAndroid Kernelunaffected
Weakness

CWE details

CWE-200

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