LiveActive security incident?Get immediate response
CVE Record

CVE-2019-14194: 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_read_reply when calling store_block in the NFSv2 case.

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-14194 affects Das U-Boot through 2019.07. A flaw in NFSv2 reply handling can copy too much data after a failed length check, potentially compromising devices during network boot or NFS-based bootloader activity.

Executive priority

Treat this as a high-priority firmware exposure for devices that use network boot. Business urgency depends on whether affected U-Boot versions and NFS boot paths exist in production environments.

Technical view

The issue is an unbounded memcpy in nfs_read_reply when store_block is called for the NFSv2 case. The provided sources describe U-Boot through 2019.07 and reference an NFS remote-code-execution analysis, but no CVSS score or CWE is supplied.

Likely exposure

Exposure is most likely in embedded, industrial, or appliance firmware using Das U-Boot through 2019.07 with NFSv2 boot or file loading enabled. Product impact must be confirmed through vendor firmware advisories, SBOMs, or bootloader version evidence.

Exploitation context

The bundle does not show CISA KEV listing or confirmed active exploitation. The referenced Semmle material characterizes the issue as an NFS RCE vulnerability, implying risk when vulnerable U-Boot processes malicious or unsafe NFS replies.

Researcher notes

Evidence is limited to the CVE description and referenced public materials. Do not generalize to all U-Boot deployments; validate NFSv2 bootloader code paths and vendor-specific firmware status before rating exposure.

Mitigation direction

  • Identify products and firmware containing Das U-Boot through 2019.07.
  • Check vendor advisories for fixed firmware or supported bootloader updates.
  • Disable NFS boot or NFSv2 bootloader paths where not operationally required.
  • Restrict boot networks to trusted, managed infrastructure only.
  • Prioritize remediation for devices exposed to shared or untrusted boot networks.

Validation and detection

  • Confirm bootloader version from firmware metadata, vendor SBOMs, or device inventory.
  • Review boot configuration for NFS or NFSv2 use during startup.
  • Check vendor guidance, including Siemens advisory SSA-577017 where applicable.
  • Verify network controls limit bootloader access to trusted NFS services.
  • Document devices where bootloader version cannot be confirmed.
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-14194 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.