LiveActive security incident?Get immediate response
CVE Record

CVE-2019-14195: 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 unvalidated length at nfs_readlink_reply in the "else" block after calculating the new path length.

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-14195 is a memory safety flaw in Das U-Boot through 2019.07, tied to NFS readlink reply handling. If a device uses affected U-Boot code in a reachable network-boot path, malformed NFS data could threaten boot integrity. Source evidence does not confirm active exploitation or a universal patch status.

Executive priority

Treat this as a targeted firmware exposure issue, not a broad internet-facing server emergency. Prioritize asset owners for embedded and industrial devices, especially where network boot is used or vendor advisories confirm impact.

Technical view

The CVE describes an unbounded memcpy with unvalidated length in nfs_readlink_reply, in the else branch after new path length calculation. The referenced Semmle article characterizes the issue as a U-Boot NFS remote code execution vulnerability, but this bundle provides no CVSS, CWE, exploit telemetry, or product-specific affected list.

Likely exposure

Exposure is most likely in embedded, industrial, or appliance firmware using Das U-Boot through 2019.07 with NFS-related boot functionality present or enabled. Product impact depends on OEM firmware composition and configuration.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Risk is contextual: U-Boot runs early in the boot chain, and NFS parsing occurs before normal operating-system controls may apply.

Researcher notes

The public bundle is sparse: no CVSS vector, CWE, patch commit, or confirmed product matrix is included. Do not assume all U-Boot-based products are reachable or exploitable; validate firmware version, compiled features, and boot path exposure.

Mitigation direction

  • Inventory firmware using Das U-Boot through 2019.07.
  • Check OEM, upstream U-Boot, and Siemens advisory guidance for fixed firmware.
  • Prioritize devices where NFS or network boot is enabled.
  • Restrict boot networks to trusted infrastructure where supported.
  • Track vendor firmware updates through normal change control.

Validation and detection

  • Confirm U-Boot version from firmware manifests or vendor SBOMs.
  • Review boot configuration for NFS or network boot usage.
  • Check vendor advisories for affected product confirmation.
  • Verify deployed firmware matches vendor-fixed releases when available.
  • Record non-exposure evidence for devices without U-Boot or NFS boot paths.
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-14195 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.