basicsecurity.net
Proof, not just disclosure.
Threats / Samsung / CVE-2023-21492
CVE-2023-21492 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Samsung Mobile Devices vulnerability

Samsung mobile devices running Android 11, 12, and 13 contain a log file information disclosure vulnerability allowing privileged local attackers to bypass ASLR protections.

Verdict

Today item — known-exploited.

A privileged local attacker can exploit CWE-532 (insertion of sensitive information into log files) on affected Samsung devices to leak memory layout information and circumvent address space layout randomization, facilitating further exploitation.

CISA KEV Yes · 2023-05-193EPSS 0.02554 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
4 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
docs.google.com ↗cisa.gov ↗ti.qianxin.com ↗storage.googleapis.com ↗Confirmed
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2023-05-19).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.02554 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
FIRST EPSS ↗High
Severity / affected
Affected: Samsung, Mobile Devices. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-532 CWE-532.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-532 · CWE-532
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I gain privileged local access to the device and read sensitive memory address information from log files.
Business
Device security controls designed to prevent code execution attacks are weakened through information disclosure.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I use the leaked address space information to bypass ASLR and craft reliable exploits against other vulnerabilities.
Business
Attackers can chain this vulnerability with other flaws to achieve arbitrary code execution with higher reliability.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 4 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by Samsung Mobile (CNA)

    • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
    • Disclosure & credit2
    Catalogued by Samsung MobileCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.