CVE-2019-14204
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 · uneditedAn issue was discovered in Das U-Boot through 2019.07. There is a stack-based buffer overflow in this nfs_handler reply helper function: nfs_umountall_reply.
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 confidenceA stack-based buffer overflow vulnerability exists in Das U-Boot's NFS handler reply helper function nfs_umountall_reply. This flaw allows remote attackers to overflow a buffer on the stack via crafted NFS replies, potentially executing arbitrary code with the privileges of the U-Boot process.
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<= 2019.07CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check the U-Boot versionAt the U-Boot prompt, type 'version' to display the installed U-Boot version and build date. Compare this to the affected range: any version <= 2019.07 is vulnerable.Affected if The version number displayed is 2019.07 or earlier (e.g., 2019.04, 2018.x, etc.)
-
Verify if NFS support is compiled into U-BootAt the U-Boot prompt, type 'setenv' and review the environment variables. Look for NFS-related variables such as 'nfsboot', 'bootargs' containing 'nfs://', or 'netboot'. Alternatively, check the U-Boot configuration file (defconfig) for CONFIG_CMD_NFS or CONFIG_NFS.Affected if NFS-related environment variables or configuration options are present, indicating NFS functionality is enabled.
-
Check if the device uses NFS for bootingReview the boot command or boot script configured in U-Boot. Look for boot commands that invoke 'nfs' or mount NFS shares, such as 'run nfsboot' or 'bootp ${kernel_addr} nfs://...'.Affected if The boot process involves mounting or accessing NFS shares, meaning the device acts as an NFS client.
-
Confirm the device is network-accessibleAt the U-Boot prompt, type 'printenv ipaddr' or 'printenv serverip' to confirm network settings are configured. This indicates the device has network connectivity that could be exploited.Affected if Network IP addresses (ipaddr, serverip) are configured, enabling potential remote attack vectors.
A user is affected if their U-Boot version is 2019.07 or earlier AND NFS functionality is enabled and accessible on the network.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade Das U-Boot to a version beyond 2019.07 which contains the patched bounds checking in nfs_umountall_reply. If upgrading is not feasible, disable NFS functionality in U-Boot and restrict network access to affected devices.
- Consultation3.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,568.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14204 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-14204 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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