CVE-2024-31162
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 specific function parameter of ASUS Download Master does not properly filter user input. An unauthenticated remote attacker with administrative privileges can exploit this vulnerability to execute arbitrary system commands on the device.
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 confidenceThis is a command injection vulnerability in ASUS Download Master where a specific function parameter fails to properly filter user input. An unauthenticated remote attacker with administrative privileges can exploit this to execute arbitrary system commands on the affected device.
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
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Confirm ASUS Download Master is installedAccess the router's web administration interface and navigate to the Download Master settings page, or check for the 'DownloadMaster' process/service running on the device via SSH or the web UI status page.Affected if Download Master is not present or not installed, the device is not affected.
-
Identify the Download Master versionIn the Download Master settings page, look for a version number displayed in the UI (often near the bottom or in an 'About' section). Alternatively, check the firmware release notes or changelog for your ASUS router model.Affected if You cannot determine the version or the installed version falls within the vulnerable range (if published by ASUS).
-
Verify web interface accessibilityDetermine if the router's web interface (which hosts Download Master) is accessible from the WAN/internet. Check router firewall settings under 'WAN' or 'External Access' settings. Attempt to access the Download Master URL from an external network if safe to do so.Affected if The Download Master web interface is exposed to untrusted networks (WAN/Internet), increasing exploitability.
-
Check administrative account securityReview the list of administrative accounts in the router's user management settings. Verify that default credentials are not in use and that strong, unique passwords are set for all admin accounts.Affected if Default credentials are in use, or administrative accounts have weak/guessable passwords, making exploitation feasible.
-
Inspect for unauthorized configuration changesReview the Download Master configuration for any unexpected or unauthorized download tasks, network settings, or custom scripts that may indicate prior exploitation.Affected if Unexpected download tasks, scripts, or network configurations are found that you did not create.
The device is likely affected if ASUS Download Master is installed, the web interface is exposed to untrusted networks, and administrative access is not properly secured with strong credentials.
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-supplied firmware patch when available; if unavailable, restrict network access to the Download Master interface and consider disabling the service if not required.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31162 — 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-31162 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