CVE-2024-41589
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 Vigor310 devices through 4.3.2.6 use unencrypted HTTP for authentication requests.
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 Vigor310 devices through version 4.3.2.6 transmit user authentication credentials over unencrypted HTTP connections, allowing remote attackers on the same network or in a man-in-the-middle position to intercept plaintext usernames and passwords during the login process.
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.3.2.6CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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 device model and firmware versionAccess the router web interface or use SNMP/CLI to retrieve the system information. Look for the model number (Vigor310 or Vigor3910) and firmware version displayed on the status/dashboard page.Affected if The device is a DrayTek Vigor310 or Vigor3910 with firmware version 4.3.2.6 or lower.
-
Verify HTTP is enabled for web managementAttempt to access the router login page using HTTP (http://<router-ip>). Check if the interface loads over an unencrypted connection.Affected if The router web management interface is accessible over HTTP (port 80).
-
Confirm HTTPS is not enforced for authenticationCheck the router web interface settings under Administration or System Maintenance. Look for options related to HTTPS enable, HTTP redirect to HTTPS, or SSL/TLS settings.Affected if HTTP access is permitted and HTTPS is not enforced for the login/authentication process.
-
Inspect login traffic for plaintext credentialsUse a packet capture tool (such as Wireshark or tcpdump) on the network segment between the client and the router. Perform a login attempt and examine the HTTP POST request for username and password fields.Affected if The login POST request transmits credentials in plaintext over HTTP rather than being encrypted via HTTPS.
A user is affected if they have a DrayTek Vigor310 or Vigor3910 router running firmware version 4.3.2.6 or lower AND the web management interface is accessible over HTTP without HTTPS enforcement.
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 dataEnable HTTPS for the web management interface if supported by the firmware, or upgrade to a firmware version that enforces encrypted authentication. If neither is possible, restrict management access to a trusted network or VPN.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-41589 — 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-41589 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