LiveActive security incident?Get immediate response
CVE Record

CVE-2020-13799: Western Digital has identified a security vulnerability in the Replay Protected Memory Block (RPMB) protoco...

Western Digital has identified a security vulnerability in the Replay Protected Memory Block (RPMB) protocol as specified in multiple standards for storage device interfaces, including all versions of eMMC, UFS, and NVMe. The RPMB protocol is specified by industry standards bodies and is implemented by storage devices from multiple vendors to assist host systems in securing trusted firmware. Several scenarios have been identified in which the RPMB state may be affected by an attacker without the knowledge of the trusted component that uses the RPMB feature.

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

Security readout for executives and security teams

Plain-English summary

This CVE describes a weakness in the RPMB storage security protocol used across eMMC, UFS, and NVMe standards. In some cases, an attacker may alter RPMB-related state without the trusted component noticing. The bundle does not identify specific affected products, severity, or confirmed exploitation.

Executive priority

Treat this as a platform supply-chain risk requiring inventory and vendor follow-up, not an emergency exploitation event based on current evidence. Priority should increase for products where trusted firmware security depends on RPMB state.

Technical view

CVE-2020-13799 concerns replay-related weaknesses in the standardized RPMB protocol. Western Digital says multiple storage interface standards and multi-vendor implementations may be relevant. The reported impact is unauthorized changes to RPMB state outside the trusted component’s awareness. No CVSS, CWE, affected CPEs, or vendor-specific fix details are provided in the bundle.

Likely exposure

Exposure is most plausible where systems rely on RPMB-backed state to protect trusted firmware or security decisions on eMMC, UFS, or NVMe storage. Product-level exposure cannot be determined from the provided CVE data because affected vendor, product, and version fields are listed as n/a.

Exploitation context

The source bundle does not show CISA KEV listing or other evidence of active exploitation. The issue is protocol-level and replay-related, but the provided sources do not include exploit availability, attack prerequisites, or observed abuse.

Researcher notes

The key gap is specificity: the CVE names standards and protocol behavior, not products, versions, CVSS, CWE, or patches. Analysis should focus on vendor advisories and whether a platform’s trusted component can detect RPMB state manipulation.

Mitigation direction

  • Inventory systems using RPMB with eMMC, UFS, or NVMe storage.
  • Check CERT/CC, Western Digital, OEM, and storage vendor guidance for model-specific action.
  • Apply platform, firmware, and storage updates only from trusted vendor channels.
  • Do not treat this as Western Digital-only exposure; the protocol is multi-vendor.
  • Review trusted firmware designs that depend on RPMB state integrity.

Validation and detection

  • Identify devices and platforms that expose or rely on RPMB.
  • Confirm whether trusted firmware uses RPMB for rollback or state protection.
  • Map storage models and firmware versions to vendor advisories.
  • Track whether vendors publish mitigations for affected implementations.
  • Document unsupported or unverifiable systems as residual risk.
Prepared
Confidence
medium
Sources
4

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.

cve · low confidence lookup

CVE-2020-13799 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
3Source 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.