LiveActive security incident?Get immediate response
CVE Record

CVE-2020-25054: An issue was discovered on Samsung mobile devices with software through 2020-04-02 (Exynos modem chipsets).

An issue was discovered on Samsung mobile devices with software through 2020-04-02 (Exynos modem chipsets). There is a heap-based buffer over-read in the Shannon baseband. The Samsung ID is SVE-2020-17239 (August 2020).

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-25054 is a Samsung mobile device vulnerability affecting Exynos modem chipset software through April 2, 2020. The issue is in the Shannon baseband and involves reading past intended heap memory. Business urgency depends on whether older Samsung devices or images remain in use.

Executive priority

Medium operational priority if legacy Samsung mobile devices remain in business use; otherwise monitor. The lack of severity scoring and exploitation evidence limits urgency, but baseband vulnerabilities can be hard to monitor directly.

Technical view

The CVE describes a heap-based buffer over-read in Samsung's Shannon baseband on mobile devices using Exynos modem chipsets. The Samsung tracking ID is SVE-2020-17239 from August 2020. The bundle provides no CVSS score, CWE, affected model list, exploit vector, or detailed impact.

Likely exposure

Exposure is most plausible for Samsung mobile devices with Exynos modem chipsets running software through April 2, 2020. The source bundle does not identify exact models, carrier builds, firmware branches, or CPEs, so inventory validation is required.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not listed as KEV in the bundle. No exploit maturity, trigger conditions, or attack path are provided. Treat exploitation status as unknown, not confirmed active.

Researcher notes

Key gaps are exact affected models, CVSS, trigger surface, impact boundaries, and patch mapping. Use Samsung's SVE-2020-17239 advisory trail as the authoritative source before making claims about exploitability or remediation completeness.

Mitigation direction

  • Check Samsung guidance for SVE-2020-17239 and affected device details.
  • Update eligible Samsung devices to vendor-supported security firmware.
  • Retire or isolate devices that cannot receive relevant Samsung updates.
  • Prioritize managed fleets containing older Exynos-based Samsung devices.

Validation and detection

  • Inventory Samsung mobile devices by model, chipset, and security patch level.
  • Identify devices running software dated April 2, 2020 or earlier.
  • Confirm whether Samsung lists each model under SVE-2020-17239 coverage.
  • Document devices without available vendor update paths.
Prepared
Confidence
medium
Sources
3

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.

cve · low confidence lookup

CVE-2020-25054 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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