CVE-2024-8075
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 · uneditedA vulnerability has been found in TOTOLINK AC1200 T8 4.1.5cu.862_B20230228 and classified as critical. Affected by this vulnerability is the function setDiagnosisCfg. The manipulation leads to os command injection. The attack can be launched remotely. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceOS command injection vulnerability in TOTOLINK AC1200 T8 router firmware 4.1.5cu.862_B20230228. The setDiagnosisCfg function fails to properly sanitize user input, allowing remote attackers to execute arbitrary operating system commands on the device.
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= 4.1.5cu.862_b20230228CVSS 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 router modelAccess the router web interface or check the device label/marketing to confirm it is a Totolink T8 AC1200 routerAffected if The device is not a Totolink T8 router, then this specific CVE does not apply
-
Check the firmware versionLog into the router web interface and navigate to System Status or Administration > Firmware Upgrade to view the current firmware version. Alternatively, check the kernel or system logs for version strings matching '4.1.5cu.862_B20230228'Affected if The installed firmware version is exactly 4.1.5cu.862_B20230228, indicating the device is running the vulnerable version
-
Verify the diagnostic feature is accessibleLocate the network diagnostics or ping functionality in the router web interface (often under System Tools > Diagnostics or Network > Ping Test). The setDiagnosisCfg function handles this feature.Affected if The diagnostic/ping testing feature is present and accessible on the router, which is where the command injection occurs
-
Inspect HTTP request patternsIf you have access to router logs or network traffic logs, review HTTP POST requests to the router for unusual or suspicious patterns in the ping/traceroute parameters that may indicate command injection attemptsAffected if Unexpected shell metacharacters (such as ;, |, &, $(), or backticks) are found in diagnostic-related HTTP requests to the router
You are affected if you are running a Totolink T8 AC1200 router with firmware version 4.1.5cu.862_B20230228 and the router's diagnostic/ping feature is accessible.
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 dataSince the vendor did not respond to the disclosure and no patch is available, implement network segmentation to isolate the router, deploy WAF rules to detect/block command injection patterns in HTTP requests, and consider replacing the device with a supported model.
- Consultation3.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8075 — 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-8075 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