NuttxApplication · Apache
CVE-2020-17528
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 · uneditedOut-of-bounds Write vulnerability in TCP stack of Apache NuttX (incubating) versions up to and including 9.1.0 and 10.0.0 allows attacker to corrupt memory by supplying arbitrary urgent data pointer offsets within TCP packets including beyond the length of the packet.
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 confidenceOut-of-bounds Write vulnerability in the TCP stack of Apache NuttX allows an attacker to supply arbitrary urgent data pointer offsets within TCP packets, including offsets beyond the packet length, leading to memory corruption.
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
NuttxApplication
<= 9.1.0= 10.0.0CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Identify Apache NuttX versionRun 'uname -v' or check the NuttX version header file (typically nuttx/version.h or include/nuttx/version.h) to determine the installed versionAffected if Version is 9.1.0 or earlier, or exactly 10.0.0
-
Verify TCP networking is enabledInspect the NuttX configuration file (defconfig or .config) for CONFIG_NET=y and CONFIG_NET_TCP=y to confirm TCP stack is compiled inAffected if TCP networking is not enabled (the vulnerability only applies when TCP is active)
-
Confirm TCP urgent data processing is in useCheck configuration for CONFIG_NET_TCP_URBITS=y or look for code that utilizes SO_OOBINLINE socket option or sends urgent data via TCPAffected if TCP urgent data processing is enabled and the system handles TCP urgent pointers (POSIX OOB data)
-
Identify TCP packet handling pathsReview network driver code or netstack logs for incoming TCP packets with URG flag set and urgent pointer valuesAffected if The system processes TCP packets with urgent data indicators
You are affected if running Apache NuttX version 9.1.0 or earlier, or exactly 10.0.0, and your system has TCP networking with urgent data processing enabled and actively handles TCP packets with urgent flags.
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 Apache NuttX to a version beyond 10.0.0 that contains the patch. Until then, minimize network exposure and disable TCP urgent data processing if possible.
Fix this in Nuttx
Scoped from the published advisory
- Consultation4.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-17528 — 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-2020-17528 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