LiveActive security incident?Get immediate response
CVE Record

CVE-2019-14202: An issue was discovered in Das U-Boot through 2019.07.

An issue was discovered in Das U-Boot through 2019.07. There is a stack-based buffer overflow in this nfs_handler reply helper function: nfs_readlink_reply.

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

Security readout for executives and security teams

Plain-English summary

CVE-2019-14202 is a stack buffer overflow in Das U-Boot, a bootloader widely used in embedded systems. The issue affects versions through 2019.07 and involves NFS reply handling. Business impact depends on whether products use vulnerable U-Boot code and expose NFS-based boot or recovery paths.

Executive priority

Prioritize assets where U-Boot is used in critical embedded or OT devices and NFS boot paths are reachable. Treat this as high urgency for exposure assessment, but do not assume active exploitation from the provided sources.

Technical view

The CVE describes a stack-based buffer overflow in the U-Boot NFS readlink reply helper, nfs_readlink_reply. The supplied Semmle reference characterizes the issue as an NFS-related U-Boot RCE vulnerability. The bundle does not provide CVSS, CWE, specific fixed version, or complete downstream vendor impact details.

Likely exposure

Likely exposure is embedded, appliance, industrial, or network devices using Das U-Boot through 2019.07, especially where NFS boot, recovery, or provisioning is reachable. Product-level exposure must be confirmed through firmware SBOMs and vendor advisories.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Public research exists, and the bug is in network-facing NFS reply parsing during U-Boot operation, which raises concern where attackers can influence boot-time network responses.

Researcher notes

Evidence is limited to the CVE description and linked public references. Avoid broad product claims: downstream exposure depends on each vendor firmware build and configuration. The absence of CVSS and KEV data lowers certainty, not potential impact.

Mitigation direction

  • Inventory firmware and devices for Das U-Boot through 2019.07.
  • Check vendor advisories for product-specific fixed firmware or mitigations.
  • Review Siemens SSA-577017 if Siemens products are in scope.
  • Restrict or disable NFS boot paths where operationally possible.
  • Isolate boot and provisioning networks from untrusted systems.
  • Monitor vendor guidance because the bundle does not name a universal fix.

Validation and detection

  • Confirm U-Boot version from firmware metadata, SBOMs, or vendor documentation.
  • Identify whether NFS boot, recovery, or provisioning is enabled.
  • Map devices that can reach NFS services during boot.
  • Check vendor advisories against exact product and firmware versions.
  • Verify compensating network isolation around boot infrastructure.
Prepared
Confidence
medium
Sources
5

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-2019-14202 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
3Timeline events
2ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
siemens-SADPADP container

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.