LiveActive security incident?Get immediate response
CVE Record

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

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2019-14193 is a memory-safety flaw in Das U-Boot through 2019.07. A malformed NFS readlink response can trigger an unbounded copy using an unvalidated length. For organizations, exposure depends on whether devices use affected U-Boot code and whether NFS boot functionality is reachable in their environment.

Executive priority

Treat this as a targeted firmware exposure review, not a broad emergency. Prioritize high-value or hard-to-replace embedded devices, especially where NFS boot features exist. Urgency increases if vendor advisories identify deployed products as affected.

Technical view

The flaw is an unbounded memcpy in nfs_readlink_reply after new path length calculation. The CVE description identifies unvalidated length handling in Das U-Boot through 2019.07. Public bundle evidence does not provide CVSS, CWE, confirmed exploit activity, or a specific fixed version.

Likely exposure

Likely exposure is limited to systems using Das U-Boot through 2019.07, especially where NFS-related bootloader functionality is used or reachable. The bundle does not enumerate affected vendors or product models.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The Semmle reference frames the issue as an NFS remote-code-execution vulnerability, but the bundle does not include exploit details or observed attacks.

Researcher notes

Evidence is incomplete: no CVSS, CWE, affected product list, patch version, or KEV status appears in the supplied bundle. Analysis should focus on firmware provenance, NFS bootloader reachability, and vendor-specific advisory correlation rather than assuming universal U-Boot exposure.

Mitigation direction

  • Inventory devices and firmware that include Das U-Boot through 2019.07.
  • Check U-Boot and device-vendor advisories for fixed firmware or supported mitigations.
  • Disable or restrict NFS bootloader functionality where it is not operationally required.
  • Segment management and boot networks from untrusted or general-purpose networks.
  • Track Siemens ProductCERT guidance if Siemens equipment is in scope.

Validation and detection

  • Confirm U-Boot versions from firmware manifests, SBOMs, vendor notices, or device diagnostics.
  • Identify whether NFS boot paths are enabled, configured, or reachable.
  • Map exposed boot or management networks to trusted administrative zones.
  • Review vendor advisories for product-specific affected status and remediation.
  • Document systems where version or NFS usage cannot be confirmed.
Prepared
Confidence
medium
Sources
6

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-14193 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
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.