LiveActive security incident?Get immediate response
CVE Record

CVE-2019-14198: 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 NFSv3 case.

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-14198 affects Das U-Boot through 2019.07 in its NFSv3 handling. A malformed NFS reply could trigger unsafe memory copying during bootloader network file loading. Business risk depends heavily on whether products expose U-Boot NFS boot or recovery paths.

Executive priority

Treat this as a targeted embedded-device exposure review, not a broad enterprise emergency. Prioritize assets that combine old U-Boot, enabled NFS boot paths, and untrusted network reachability.

Technical view

The CVE describes an unbounded memcpy caused by a failed length check in nfs_read_reply when store_block is called for NFSv3. The bundle does not provide CVSS, CWE, complete affected product mappings, or confirmed patch details.

Likely exposure

Exposure is most plausible in embedded or industrial devices using Das U-Boot through 2019.07 with NFSv3 network boot, recovery, or provisioning enabled. The bundle lists Siemens advisory coverage but no complete affected-product inventory.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. The Semmle reference title indicates remote-code-execution relevance, but this assessment cannot confirm exploit availability from the provided bundle alone.

Researcher notes

The useful lead is the NFSv3 nfs_read_reply to store_block length-validation failure. Evidence is incomplete on scoring, exact fixed commits, and downstream product impact, so validation should be tied to firmware provenance and vendor advisories.

Mitigation direction

  • Identify products and firmware using Das U-Boot through 2019.07.
  • Check vendor advisories for device-specific fixed firmware or backports.
  • Disable NFSv3 boot or recovery paths where not required.
  • Restrict bootloader network access to trusted provisioning networks.
  • Prioritize updates for remotely managed or physically exposed embedded devices.

Validation and detection

  • Inventory firmware builds and bootloader versions across affected device classes.
  • Confirm whether NFSv3 boot, update, or recovery is enabled.
  • Review Siemens SSA-577017 for product-specific applicability.
  • Verify deployed firmware includes vendor-approved remediation or a newer unaffected U-Boot baseline.
  • Document compensating network controls where firmware updates are unavailable.
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-14198 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.