Security readout for executives and security teams
Plain-English summary
This CVE describes a Samsung mobile-device flaw affecting Android Q (10.0) devices with Exynos990 chipsets. The Secure Element chip may be vulnerable to a buffer overflow, potentially allowing arbitrary code execution and sensitive information access. Public severity scoring is not provided in the bundle.
Executive priority
Prioritize confirmation in mobile fleets, especially legacy Samsung devices that may no longer receive updates. Business urgency is driven by sensitive-data exposure and possible code execution, but public risk scoring and exploitation evidence are incomplete.
Technical view
CVE-2020-28341 is tied to Samsung SVE-2020-18632 from November 2020. The issue is a buffer overflow in the S3K250AF Secure Element CC EAL 5+ chip on Samsung mobile devices with Q (10.0) and Exynos990 chipsets. No CVSS, CWE, or detailed affected product list is provided.
Likely exposure
Exposure appears limited to Samsung mobile devices running Android Q (10.0) on Exynos990 chipsets. The affected-products metadata is incomplete, so teams should validate by device model, chipset, OS version, security patch level, and Samsung bulletin applicability.
Exploitation context
The source bundle does not show CISA KEV listing, active exploitation, public exploit availability, or attack prerequisites. Treat exploitation status as unconfirmed. The stated impact, if reachable, includes arbitrary code execution and sensitive information disclosure.
Researcher notes
Public evidence is sparse: no CVSS vector, CWE, detailed advisory text, exploit status, or complete CPE list is included. Analysis should stay anchored to Samsung SVE-2020-18632 and avoid assuming affected models beyond Android Q Exynos990 devices described in the CVE.
Mitigation direction
- Check Samsung guidance for SVE-2020-18632 and CVE-2020-28341 applicability.
- Apply relevant Samsung mobile security updates where available.
- Prioritize legacy Android 10 Exynos990 devices in managed mobile fleets.
- Retire or isolate devices that cannot receive applicable vendor updates.
Validation and detection
- Inventory Samsung mobile devices by model, OS version, chipset, and patch level.
- Identify devices running Android Q (10.0) with Exynos990 chipsets.
- Compare device patch levels against Samsung's November 2020 security update guidance.
- Document exceptions where affected status cannot be confirmed from vendor data.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2020-28341 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://security.samsungmobile.com/securityUpdate.smsbCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.