CVE-2024-45890
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 · uneditedDrayTek Vigor3900 1.5.1.3 contains a post-authentication command injection vulnerability This vulnerability occurs when the `action` parameter in `cgi-bin/mainfunction.cgi` is set to `download_ovpn.`
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 confidenceDrayTek Vigor3900 router firmware 1.5.1.3 contains a command injection vulnerability in the web interface CGI script (mainfunction.cgi). When the 'action' parameter is set to 'download_ovpn', the application fails to properly sanitize input before passing it to system shell commands, allowing authenticated attackers to execute arbitrary commands on the underlying operating system.
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= 1.5.1.3CVSS 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 device modelAccess the router web interface or check the device label/marketing to confirm it is a DrayTek Vigor3900 modelAffected if The device is not a DrayTek Vigor3900 (not affected)
-
Check firmware versionLog into the web interface and navigate to System Maintenance > Firmware Upgrade, or use SNMP/CLI to retrieve the running firmware versionAffected if Firmware version is exactly 1.5.1.3 (vulnerable)
-
Verify web interface accessibilityConfirm the mainfunction.cgi script is accessible via HTTP/HTTPS on the router (typically at /cgi-bin/mainfunction.cgi)Affected if The CGI script is accessible without additional authentication beyond standard web login (potentially vulnerable)
-
Check OpenVPN configurationIn the web interface, navigate to VPN and Remote Access > Remote Dial-In or VPN > OpenVPN settings to see if any OpenVPN configurations exist using the download_ovpn featureAffected if Any OpenVPN client or server profile is configured that could trigger the download_ovpn action
The environment is affected if the device is a DrayTek Vigor3900 running firmware version 1.5.1.3 and the web interface with mainfunction.cgi is accessible to attackers.
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 dataRestrict administrative access to the DrayTek Vigor3900 web interface to trusted networks only, enforce strong credentials, and monitor for unauthorized access attempts. Apply vendor firmware updates when available.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45890 — 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-45890 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