NetusbApplication · Kcodes
CVE-2015-3036
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 · uneditedStack-based buffer overflow in the run_init_sbus function in the KCodes NetUSB module for the Linux kernel, as used in certain NETGEAR products, TP-LINK products, and other products, allows remote attackers to execute arbitrary code by providing a long computer name in a session on TCP port 20005.
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 confidenceStack-based buffer overflow in the run_init_sbus function in the KCodes NetUSB Linux kernel module allows remote attackers to execute arbitrary code via a long computer name sent on TCP port 20005. The vulnerability affects specific NETGEAR and TP-LINK products using this kernel module.
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
NetusbApplication
all versionsCVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 the device vendor and modelDetermine if the system is a NETGEAR or TP-LINK product, as these are the known affected vendors for this vulnerabilityAffected if The device is a NETGEAR or TP-LINK product using the KCodes NetUSB kernel module
-
Check if the NetUSB kernel module is loadedRun 'lsmod | grep netusb' or 'modinfo netusb' to see if the NetUSB kernel module is present and loadedAffected if The NetUSB kernel module is loaded on the system
-
Verify TCP port 20005 is listeningRun 'netstat -tlnp | grep 20005' or 'ss -tlnp | grep 20005' to check if port 20005 is open and listeningAffected if TCP port 20005 is open and listening on the system
-
Check for external network exposure of port 20005Review firewall rules with 'iptables -L -n' or similar to determine if port 20005 is accessible from external network interfacesAffected if Port 20005 is accessible from untrusted network interfaces
-
Review network connections to port 20005Monitor network traffic or check active connections on port 20005 for suspicious or unexpected originsAffected if There are connections from untrusted sources to port 20005
The system is affected if it is a NETGEAR or TP-LINK device with the KCodes NetUSB module loaded and TCP port 20005 exposed 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 dataApply vendor-supplied firmware patches when available; until then, block TCP port 20005 at network firewalls or disable the NetUSB service if possible.
Fix this in Netusb
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-3036 — 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-2015-3036 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