CVE-2024-32946
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 · uneditedA vulnerability in the LevelOne WBR-6012 router's firmware version R0.40e6 allows sensitive information to be transmitted in cleartext via Web and FTP services, exposing it to network sniffing attacks.
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 confidenceThe LevelOne WBR-6012 router firmware version R0.40e6 transmits sensitive information in cleartext over both Web (HTTP) and FTP services. This allows attackers on the same network segment to capture credentials, configuration data, or other sensitive traffic through passive network sniffing. The vulnerability stems from the use of unencrypted protocols instead of their secure counterparts (HTTPS, SFTP/FTPS).
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= r0.40e6CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
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 firmware versionAccess the router's administrative interface or check the device status page to confirm the exact firmware version. Alternatively, check the firmware file metadata or the vendor's download page for the installed version.Affected if The installed firmware version is r0.40e6 exactly.
-
Verify HTTP service accessibilityAttempt to access the router's web interface using HTTP (port 80) from a browser or command line: http://[router-ip]. Use a network port scanner (e.g., nmap) to check if port 80 is open: nmap -p 80 [router-ip].Affected if Port 80 (HTTP) is open and the router responds to unencrypted HTTP requests.
-
Verify FTP service accessibilityUse a network port scanner to check if port 21 is open: nmap -p 21 [router-ip]. Alternatively, attempt an FTP connection: ftp [router-ip].Affected if Port 21 (FTP) is open and the router accepts unencrypted FTP connections.
-
Check for HTTPS availabilityAttempt to access the router's web interface using HTTPS (port 443): https://[router-ip]. Use nmap to check if port 443 is open: nmap -p 443 [router-ip].Affected if HTTPS (port 443) is not available or not responding, forcing the use of unencrypted HTTP.
-
Check for SFTP/FTPS availabilityUse nmap to check if ports 22 (SFTP), 989, or 990 (FTPS) are open on the router: nmap -p 22,989,990 [router-ip].Affected if No secure file transfer options (SFTP/FTPS) are available, only unencrypted FTP.
If the router runs firmware r0.40e6 and exposes accessible HTTP (port 80) or FTP (port 21) services without HTTPS or SFTP/FTPS alternatives, sensitive credentials and configuration data could be intercepted by anyone on the same network segment.
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 encrypted alternatives by configuring the router's Web interface for HTTPS access and replacing unencrypted FTP with SFTP or FTPS. If the vendor has released a patched firmware version, upgrade to the latest supported release.
- 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-32946 — 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-32946 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