LiveActive security incident?Get immediate response
CVE Record

CVE-2019-14197: 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 read of out-of-bounds data at nfs_read_reply.

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

Security readout for executives and security teams

Plain-English summary

CVE-2019-14197 is a Das U-Boot bootloader issue affecting versions through 2019.07. The published record describes an out-of-bounds read in NFS reply handling. Business risk depends on whether products use this U-Boot code path, especially firmware that can boot or fetch data over NFS.

Executive priority

Prioritize inventory and vendor validation for exposed embedded or OT devices. Treat confirmed use of affected U-Boot with reachable NFS boot paths as a firmware remediation item, but urgency cannot be precisely rated from the provided sources alone.

Technical view

The CVE record identifies an out-of-bounds data read at nfs_read_reply in Das U-Boot through 2019.07. Public references include the U-Boot project, Semmle research on an NFS-related U-Boot vulnerability, and a Siemens advisory. The bundle does not provide CVSS, CWE, exact product CPEs, or confirmed fixed versions.

Likely exposure

Likely exposure is embedded, appliance, industrial, or OT firmware using Das U-Boot through 2019.07 with NFS functionality present. The bundle lists affected products as unavailable, so product-level exposure requires firmware SBOM, vendor advisory, or source review.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Semmle published research on an NFS-related U-Boot vulnerability, but this analysis should not assume real-world exploitation without additional evidence.

Researcher notes

Key unknowns are exact vulnerable commit range, fixed release, reachable attack surface, and product mappings. Focus analysis on nfs_read_reply, U-Boot versions through 2019.07, and downstream vendor firmware integration rather than assuming generic Linux exposure.

Mitigation direction

  • Identify firmware builds containing Das U-Boot through 2019.07.
  • Check vendor advisories, including Siemens guidance, for product-specific updates.
  • Upgrade U-Boot or device firmware when vendor-supported fixes are available.
  • Disable unused NFS boot or network boot paths where operationally safe.
  • Restrict bootloader network access to trusted management networks.

Validation and detection

  • Review firmware SBOMs or build manifests for U-Boot versions.
  • Confirm whether NFS boot support is compiled or enabled.
  • Check vendor advisory applicability for each device model and firmware version.
  • Verify compensating network controls around bootloader-accessible services.
  • Track remediation status in asset inventory and exception records.
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-14197 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.