CVE-2022-47208
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 · uneditedThe “puhttpsniff” service, which runs by default, is susceptible to command injection due to improperly sanitized user input. An unauthenticated attacker on the same network segment as the router can execute arbitrary commands on the device without authentication.
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 confidenceThe puhttpsniff service, which runs by default on the affected router, contains a command injection vulnerability due to improperly sanitized user input. An unauthenticated attacker on the same network segment can exploit this to execute arbitrary commands on the device without any authentication required.
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.9.90< 1.0.9.90< 1.0.9.90< 1.0.9.90< 1.0.9.90< 1.0.9.90CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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.
-
Identify the Netgear Nighthawk modelAccess the router admin interface or check the device label to confirm the exact model number (Ax1800, Ax2400, Ax3000, Ax5400, Ax6000, or Ax11000)Affected if The device is not one of these six Nighthawk models, then it is not affected by this specific CVE
-
Check the installed firmware versionLog into the router web interface and navigate to Administration > Firmware Update or check the current version displayed on the status page. Compare against version 1.0.9.90Affected if The firmware version is below 1.0.9.90, meaning the device is within the affected version range
-
Verify the puhttpsniff service is enabledAccess the router via SSH or telnet if enabled, then check running processes or services for puhttpsniff. Alternatively, inspect the router's service configuration via the admin interface if service status is visibleAffected if The puhttpsniff service is running (it runs by default on affected routers), which is required for the command injection to be exploitable
-
Assess network exposureDetermine if the router management interface (HTTP/HTTPS ports 80/443) is accessible from untrusted network segments. Check NAT/firewall rules and whether the router is deployed on a restricted management VLANAffected if The router admin interface is accessible from the same network segment where untrusted users reside, allowing unauthenticated attackers to reach the vulnerable service
The device is affected if it is a Netgear Nighthawk model (Ax1800/2400/3000/5400/6000/11000) running firmware below version 1.0.9.90, the puhttpsniff service is active, and the management interface is reachable from an untrusted network segment.
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.
dbcve · scoped1.0.9.90
Restrict network access to the router's management interfaces to prevent unauthorized access from untrusted network segments. If available, apply vendor firmware updates to patch the command injection vulnerability or disable the puhttpsniff service if not required.
Upgrade to Nighthawk firmware version 1.0.9.90 or later for your specific model (Ax1800, Ax2400, Ax3000, Ax5400, Ax6000, or Ax11000)
- Identify your Nighthawk router model (Ax1800, Ax2400, Ax3000, Ax5400, Ax6000, or Ax11000)
- Access the router's web management interface by navigating to routerlogin.net or 192.168.1.1
- Log into the router with admin credentials
- Navigate to the Firmware Update or Administration section
- Check the current firmware version under Router Info or System Summary
- If firmware version is below 1.0.9.90, download the latest firmware version 1.0.9.90 or later from the official NETGEAR support website for your specific model
- In the firmware update section, upload the downloaded firmware file and initiate the update
- Wait for the firmware to upload and install - do not power off the router during this process
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47208 — 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-2022-47208 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