LiveActive security incident?Get immediate response
CVE Record

CVE-2020-28343: An issue was discovered on Samsung mobile devices with P(9.0) and Q(10.0) (Exynos 980, 9820, and 9830 chips...

An issue was discovered on Samsung mobile devices with P(9.0) and Q(10.0) (Exynos 980, 9820, and 9830 chipsets) software. The NPU driver allows attackers to execute arbitrary code because of unintended write and read operations on memory. The Samsung ID is SVE-2020-18610 (November 2020).

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This CVE affects certain Samsung mobile devices using Exynos 980, 9820, or 9830 chipsets on Android 9 or 10. The flaw is in the NPU driver and may allow arbitrary code execution through unintended memory access. Severity data is incomplete, so urgency depends on device presence and patch status.

Executive priority

Prioritize asset confirmation first. If affected, unpatched devices are present in business use, treat remediation as high priority because the issue involves arbitrary code execution in a device driver.

Technical view

CVE-2020-28343 maps to Samsung SVE-2020-18610 from November 2020. The reported issue is unintended read and write operations in the Samsung NPU driver, creating arbitrary code execution risk on affected Exynos-based Samsung devices running P(9.0) or Q(10.0). No CVSS, CWE, or detailed prerequisites are provided in the bundle.

Likely exposure

Exposure is limited to Samsung mobile devices with Exynos 980, 9820, or 9830 chipsets running Android 9.0 or 10.0 software. The bundle does not identify exact device models or patched build numbers.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. Public detail is limited to the CVE description and Samsung security update reference, so exploitability conditions and attacker proximity are not confirmed here.

Researcher notes

The source bundle lacks CVSS, CWE, model-level affected lists, patched build identifiers, and exploit prerequisites. Analysis should remain bounded to Samsung Exynos 980/9820/9830 devices on Android 9 or 10 unless vendor guidance supplies more detail.

Mitigation direction

  • Identify Samsung devices with Exynos 980, 9820, or 9830 chipsets.
  • Check Samsung guidance for SVE-2020-18610 in the November 2020 security update.
  • Apply applicable Samsung mobile security updates where available.
  • Retire or restrict affected devices that cannot receive vendor updates.
  • Avoid using unpatched affected devices for sensitive corporate workflows.

Validation and detection

  • Inventory Samsung device models, Android versions, chipsets, and security patch levels.
  • Confirm whether devices run Android 9.0 or 10.0 software.
  • Map device patch status against Samsung SVE-2020-18610 guidance.
  • Verify mobile device management records show applicable updates installed.
  • Flag unsupported affected devices for replacement or compensating controls.
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.

description · low confidence lookup

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 lookup
cve · low confidence lookup

CVE-2020-28343 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.