CVE-2024-5035
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 affected device expose a network service called "rftest" that is vulnerable to unauthenticated command injection on ports TCP/8888, TCP/8889, and TCP/8890. By successfully exploiting this flaw, remote unauthenticated attacker can gain arbitrary command execution on the device with elevated privileges.This issue affects Archer C4500X: through 1_1.1.6.
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 TP-Link Archer C4500X exposes a 'rftest' network service on TCP ports 8888, 8889, and 8890 that contains an unauthenticated command injection vulnerability. Remote attackers can execute arbitrary commands with elevated privileges without any authentication required.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:N/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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.
-
Confirm device model is TP-Link Archer C4500XAccess the router web interface or check the device label to verify the exact model number matches 'Archer C4500X'.Affected if The device is a TP-Link Archer C4500X router.
-
Check if ports 8888, 8889, or 8890 are openRun a port scan from an external system or use 'netstat -an | grep -E "(8888|8889|8890)"' on the router (if CLI access is available).Affected if Any of TCP ports 8888, 8889, or 8890 are listening and accepting connections.
-
Verify network exposure of the rftest serviceDetermine whether the router's WAN interface or any IP address is reachable from untrusted networks on ports 8888-8890. Check router firewall rules and network placement.Affected if The rftest service ports are accessible from untrusted networks (such as the internet) without network filtering.
-
Check if the rftest service respondsUse a tool like 'nc' or 'telnet' to connect to the router's IP on port 8888 and observe if any banner or response is received.Affected if Connecting to port 8888, 8889, or 8890 produces a response indicating the rftest service is active.
-
Check firmware versionAccess the router administration interface (typically at 192.168.0.1 or 192.168.1.1) and navigate to the firmware or status page to identify the installed firmware version.Affected if The installed firmware version is at or below 1_1.1.6 (or is an older/unpatched version without available update).
A user is affected if they operate a TP-Link Archer C4500X with ports 8888-8890 exposed and accessible from untrusted networks, particularly on firmware versions that have not been patched beyond the vulnerability fix.
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 dataIf a firmware patch is available, update the device to a version beyond 1_1.1.6. Otherwise, block external access to ports 8888-8890 at the network perimeter and place the device in a restricted network segment.
- 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-2024-5035 — 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-2024-5035 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