CVE-2019-5017
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 exploitable information disclosure vulnerability exists in the KCodes NetUSB.ko kernel module that enables the ReadySHARE Printer functionality of at least two NETGEAR Nighthawk Routers and potentially several other vendors/products. An unauthenticated, remote attacker can craft and send a packet containing an opcode that will trigger the kernel module to return several addresses. One of which can be used to calculate the dynamic base address of the module for further exploitation.
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 confidenceAn information disclosure vulnerability exists in the KCodes NetUSB.ko kernel module used by NETGEAR Nighthawk routers for ReadySHARE Printer functionality. An unauthenticated, remote attacker can send specially crafted packets containing specific opcodes that cause the kernel module to leak memory addresses, including one that reveals the module's dynamic base address, enabling ASLR bypass for further kernel-level exploitation.
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= 1.0.4.28_10.1.54= 1.0.2.66CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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 router modelDetermine if the device is a NETGEAR Nighthawk router or other model using the KCodes NetUSB kernel module. Check the device label or administrative interface for the exact model number.Affected if Device is a NETGEAR Nighthawk or other affected model using NetUSB
-
Check firmware versionLog into the router web interface and navigate to Administration > Firmware Update or check the current version displayed on the status page. Alternatively, check the kernel module file version if you have shell access.Affected if Firmware version equals 1.0.4.28_10.1.54 on Netgear R8000
-
Check ReadySHARE Printer statusLog into the router web interface and navigate to ReadySHARE settings or USB Storage/Printer settings. Verify whether the ReadySHARE Printer feature is enabled or the USB printer is configured.Affected if ReadySHARE Printer functionality is enabled or configured
-
Verify NetUSB.ko module versionIf you have command-line access to the router (via telnet/ssh), run 'modinfo netusb.ko' or check the module file version directly. Compare the version to 1.0.2.66.Affected if NetUSB.ko module version equals 1.0.2.66
The environment is affected if the device runs NETGEAR firmware version 1.0.4.28_10.1.54 or NetUSB.ko version 1.0.2.66 with ReadySHARE Printer functionality enabled, as this specific configuration allows remote attackers to leak kernel memory addresses via crafted packets.
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 firmware updates from NETGEAR or affected device manufacturers once available. As a compensating control, isolate affected devices behind a firewall or VLAN to limit remote attack surface until patching is possible.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.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 $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5017 — 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-5017 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