CVE-2024-30645
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 · uneditedTenda AC15V1.0 V15.03.20_multi has a command injection vulnerability via the deviceName parameter.
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 Tenda AC15 V1.0 router firmware V15.03.20_multi contains a command injection vulnerability in the deviceName parameter, allowing remote attackers to inject and execute arbitrary OS 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= 15.03.20_multiCVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/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 firmware versionLog into the Tenda AC15 router admin interface and navigate to System Settings > Firmware Version, or check the version label on the device. Alternatively, use nmap or curl to probe the web interface for version information in the HTML or HTTP headers.Affected if The installed firmware version is exactly 15.03.20_multi (no other versions are listed as affected)
-
Confirm remote management is accessibleAttempt to access the router web interface from an external network location (outside the local LAN) using the router's public IP address on port 80 or 443. Check if the login page loads remotely.Affected if Remote management interface is exposed and accessible from the internet on the WAN interface
-
Check for unauthorized processes or configurationsIf you have shell access (via SSH/Telnet to the router), run 'ps' to list running processes and look for unexpected shells or commands. Inspect /var/log/ for suspicious entries in system logs.Affected if Unexpected processes are running, or logs show commands injected through the deviceName parameter that were not initiated by legitimate administration
-
Review web server access logsIf available, examine the router's HTTP server logs for requests to form processing endpoints (commonly /goform/ or /cgi-bin/) containing shell metacharacters like ; | ` $ ( ) in the deviceName parameter.Affected if Logs contain requests with command injection payloads in the deviceName parameter field
The environment is affected if the Tenda AC15 is running firmware version 15.03.20_multi and has its remote management interface exposed to the 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 dataApply the vendor-provided firmware patch when available; until then, disable remote management interfaces, restrict network access to trusted IPs, and monitor for indicator compromise.
- 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-30645 — 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-30645 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