LiveActive security incident?Get immediate response
CVE Record

CVE-2019-14192: 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 when parsing a UDP packet due to a net_process_received_packet integer underflow during an nc_input_packet call.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2019-14192 is a memory-safety flaw in Das U-Boot through 2019.07. A malformed UDP packet can trigger an integer underflow and unbounded memory copy while U-Boot processes network input. Business urgency depends on whether products use affected U-Boot builds and expose bootloader networking.

Executive priority

Treat this as an inventory-driven embedded-device risk. Prioritize internet-adjacent, field-deployed, industrial, and hard-to-patch devices using U-Boot networking. Do not assume active exploitation from this bundle alone.

Technical view

The CVE describes an integer underflow in net_process_received_packet during an nc_input_packet path, leading to unbounded memcpy while parsing a UDP packet. The bundle names Das U-Boot through 2019.07 but does not provide CVSS, CWE, fixed versions, or a complete product list.

Likely exposure

Exposure is most likely in embedded, industrial, or appliance devices shipping Das U-Boot through 2019.07 with bootloader network features reachable. The bundle does not identify specific affected vendors or configurations beyond Das U-Boot and a Siemens advisory reference.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Public references include a Semmle U-Boot RCE NFS vulnerability blog, but the provided evidence is insufficient to claim exploitation in the wild.

Researcher notes

Key evidence gaps are CVSS, CWE, fixed commit or version, affected downstream products, and exploit confirmation. Focus analysis on U-Boot through 2019.07 network packet handling and vendor firmware provenance, without extrapolating beyond cited advisories.

Mitigation direction

  • Inventory products and firmware for Das U-Boot versions through 2019.07.
  • Check U-Boot and device-vendor guidance for fixed firmware or backported patches.
  • Review the Siemens advisory if Siemens products are in scope.
  • Restrict access to bootloader network services on trusted management networks.
  • Disable unnecessary bootloader network features where vendor-supported.

Validation and detection

  • Confirm U-Boot version and vendor patch level in each firmware image.
  • Identify whether bootloader UDP or network boot features are enabled.
  • Map whether bootloader networking is reachable from untrusted networks.
  • Check vendor advisories for affected models and remediation status.
  • Document compensating controls where firmware updates are unavailable.
Prepared
Confidence
medium
Sources
5

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