dbcve.org
U BootApplication · Denx

CVE-2019-14192

CRITICAL · 9.8 CVSS v3.0 Published 2019-07-31
Fix available
A fix is available. Upgrade to after 2019.07 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

U-Boot contains an integer underflow vulnerability in net_process_received_packet during nc_input_packet handling. When processing UDP packets, the length calculation underflows, resulting in an unbounded memcpy that copies a very large amount of data into a small buffer, leading to heap/memory corruption and potential remote code execution.

MitigationUpdate U-Boot to a version containing the fix for this integer underflow; if patching is not feasible, disable network packet reception features (CONFIG_CMD_NET or related networking options) in the bootloader configuration to eliminate the attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
U BootApplication
Affected:<= 2019.07

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify U-Boot version
    Access the U-Boot prompt or check boot logs for the version string displayed at startup (typically shows 'U-Boot YYYY.MM' or similar). If you have access to the compiled U-Boot binary, use 'strings' or check the version header in the image.
    Affected if The displayed version is 2019.07 or earlier (any version up to and including 2019.07).
  2. Verify networking is enabled
    Check the U-Boot configuration file (.config) or the defconfig used to build the image for CONFIG_CMD_NET or related networking options such as CONFIG_NET, CONFIG_UDP_FUNC, or CONFIG_CMD_PING.
    Affected if CONFIG_CMD_NET, CONFIG_NET, or other networking-related configuration options are present and enabled in the U-Boot build configuration.
  3. Confirm UDP packet reception is active
    Inspect the U-Boot environment variables (run 'printenv' at the U-Boot prompt) or check boot scripts for network-related variables like 'netretry', 'autoload', or any DHCP/BOOTP configuration that triggers network packet handling at boot.
    Affected if Network auto-configuration is enabled (autoload=yes, netretry=yes, or DHCP/BOOTP requests are performed during boot).

A system is affected if it runs U-Boot version 2019.07 or earlier with any network packet reception functionality (CONFIG_CMD_NET or related) enabled in the build configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2019.07
Interim mitigation

Update U-Boot to a version containing the fix for this integer underflow; if patching is not feasible, disable network packet reception features (CONFIG_CMD_NET or related networking options) in the bootloader configuration to eliminate the attack surface.

Recommended fix Moderate confidence

U-Boot 2019.10 or later stable release

  1. 1. Identify all embedded devices or systems running U-Boot version 2019.07 or earlier
  2. 2. Check the current U-Boot version on affected systems using 'version' or 'printenv' command in U-Boot prompt, or check the build configuration
  3. 3. Obtain a patched U-Boot binary or build from source using a version newer than 2019.07 (e.g., 2019.10 or later releases)
  4. 4. For embedded devices: follow the manufacturer's firmware update procedure to flash the updated U-Boot image
  5. 5. For custom builds: rebuild U-Boot from source with the same configuration and replace the bootloader image
  6. 6. Verify the upgrade was successful by checking the U-Boot version after reboot
Caveat Upgrading U-Boot may require reconfiguration of boot parameters or board-specific settings; ensure backup of current environment variables and configuration before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in U Boot Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-14192 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-14192 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data