LiveActive security incident?Get immediate response
CVE Record

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

An issue was discovered in Das U-Boot through 2019.07. There is an unbounded memcpy with a failed length check at nfs_lookup_reply.

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

Security readout for executives and security teams

Plain-English summary

CVE-2019-14196 is a memory-safety flaw in Das U-Boot’s NFS boot handling through version 2019.07. If a product boots or fetches data over NFS using affected U-Boot code, malformed network replies could corrupt bootloader memory. The bundle does not provide CVSS scoring or confirmed active exploitation.

Executive priority

Treat this as a targeted exposure issue, not a broad internet-facing emergency from the available evidence. Prioritize environments where devices rely on network boot, recovery, or provisioning over NFS, especially operational technology or appliance fleets.

Technical view

The CVE describes an unbounded memcpy caused by a failed length check in nfs_lookup_reply. The Semmle reference characterizes the issue as an NFS-related U-Boot remote code execution vulnerability, but this assessment cannot add exploit mechanics beyond the sources.

Likely exposure

Exposure is most plausible in embedded, appliance, industrial, or custom Linux systems using Das U-Boot through 2019.07 with NFS boot or NFS file retrieval enabled. Products not using U-Boot NFS functionality are less likely exposed.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. Practical risk depends on whether an attacker can influence NFS responses during boot or recovery workflows, such as through a malicious server or compromised boot network.

Researcher notes

The CVE metadata lacks CVSS, CWE, and precise affected-product CPEs. Analysis should stay tied to Das U-Boot through 2019.07 and the nfs_lookup_reply length-check failure. Validate vendor branches because downstream firmware may backport fixes without changing obvious version strings.

Mitigation direction

  • Identify products and firmware using Das U-Boot through 2019.07.
  • Check vendor firmware, Debian LTS, and Siemens guidance for fixed packages or advisories.
  • Disable NFS boot paths where they are not operationally required.
  • Restrict boot networks to trusted servers and management segments.
  • Prioritize vendor-provided firmware updates over local bootloader changes.

Validation and detection

  • Inventory device bootloaders and record U-Boot version evidence.
  • Confirm whether NFS boot or NFS file retrieval is enabled.
  • Map exposed products to vendor advisories listed in the CVE references.
  • Check compensating controls on boot and provisioning networks.
  • Track remediation status separately for appliances, industrial systems, and custom builds.
Prepared
Confidence
medium
Sources
6

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-14196 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
5Source 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.