CVE-2024-31161
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 upload functionality of ASUS Download Master does not properly filter user input. Remote attackers with administrative privilege can exploit this vulnerability to upload any file to any location. They may even upload malicious web page files to the website directory, allowing arbitrary system commands to be executed upon browsing the webpage.
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 upload functionality in ASUS Download Master lacks proper input filtering and path validation, allowing authenticated remote attackers with administrative privileges to upload arbitrary files to any location on the filesystem. Attackers can upload malicious web page files to the web server's document directory, achieving arbitrary command execution when those pages are accessed.
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< 3.1.0.114CVSS 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.
-
Identify ASUS Download Master installationCheck if the device is an ASUS router or check for Download Master service/process on the system. Access the router web interface (typically at http://192.168.1.1) and look for the Download Master application in the administrative panel.Affected if ASUS Download Master is present on the system
-
Determine installed versionNavigate to the router's firmware version or Download Master version information within the web administration interface. Look for version details typically found in System Setup, Firmware Version, or Download Master settings.Affected if The version number is lower than 3.1.0.114
-
Verify web management interface accessibilityConfirm whether the router web interface (port 80/443) is accessible from outside the local network. Check router firewall settings, port forwarding rules, or WAN accessibility of the admin panel.Affected if The administrative web interface is exposed to untrusted networks or the internet
-
Inspect web document directory for unexpected filesIf you have CLI or FTP access to the router, examine the web server document root (typically /www or /www/user) for unfamiliar .asp, .php, .htm, or .exe files that were not intentionally deployed.Affected if Unexpected web page files or scripts exist in the web directory that were not uploaded by an administrator
A system is affected if it runs ASUS Download Master with version lower than 3.1.0.114 and has its administrative web interface accessible, potentially allowing an authenticated attacker to upload malicious files.
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.
dbcve · scoped3.1.0.114
Apply vendor-supplied firmware patches when available; meanwhile, restrict administrative interface access to trusted networks only, disable the upload feature if not required, and monitor for unauthorized file modifications.
3.1.0.114
- Obtain ASUS Download Master version 3.1.0.114 or later from the official ASUS support website
- Ensure you have administrative credentials for the Download Master installation
- Back up any existing configuration and downloaded files
- Install or apply the update to Download Master version 3.1.0.114
- Verify the installation was successful and the version number reflects 3.1.0.114 or higher
- Confirm the upload functionality is working correctly with proper file type restrictions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.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 $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31161 — 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-31161 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