CVE-2022-4498
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 · uneditedIn TP-Link routers, Archer C5 and WR710N-V1, running the latest available code, when receiving HTTP Basic Authentication the httpd service can be sent a crafted packet that causes a heap overflow. This can result in either a DoS (by crashing the httpd process) or an arbitrary code execution.
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 · moderate confidenceA heap overflow vulnerability exists in the httpd service of TP-Link Archer C5 and WR710N-V1 routers. The vulnerability is triggered via crafted HTTP Basic Authentication packets, allowing attackers to either crash the httpd process (DoS) or achieve arbitrary code execution with the privileges of the httpd service.
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= 2_160201_us= 1_151022_usCVSS 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.1/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.
-
Identify the device modelAccess the router's web interface or check the device label to confirm the exact model number is TP-Link Archer C5 or TP-Link TL-WR710NAffected if The device is not one of these two models, the vulnerability does not apply
-
Check the installed firmware versionLog into the router's web management interface and navigate to the Status or System section to view the firmware version, or use the router's admin console to run 'version' or check /etc/versionAffected if The firmware version is exactly 2_160201_us (Archer C5) or 1_151022_us (WR710N)
-
Verify the httpd web service is runningAccess the router via SSH or telnet and run 'ps' to list running processes, looking for httpd, or check if the web interface on port 80 or 443 is responsiveAffected if The httpd process is not running and the web interface is inaccessible, the attack surface does not exist
-
Confirm HTTP management is accessibleAttempt to reach the router's web interface from the network by browsing to the router's IP address, or check the router's administration settings for 'HTTP Management' or 'Remote Management' statusAffected if The HTTP Basic Authentication page is reachable, the vulnerability is potentially exploitable
A user is affected if they own a TP-Link Archer C5 (firmware 2_160201_us) or TL-WR710N (firmware 1_151022_us) with the httpd web service accessible on their 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 dataRestrict access to the router's web management interface to trusted networks only, disable remote HTTP management if not required, and monitor TP-Link for firmware updates addressing this vulnerability.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-4498 — 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-4498 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