CVE-2025-64389
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 web server of the device performs exchanges of sensitive information in clear text through an insecure protocol.
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 web server on the affected device transmits sensitive information (such as authentication credentials, session data, or personal information) in clear text over an insecure protocol, likely HTTP instead of HTTPS or unencrypted network communication. This allows attackers on the network path to intercept and read sensitive data in transit.
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
- None
- Authentication
- X
- User interaction
- A
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:L/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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.
-
Verify HTTP port accessibilityCheck if the device's web server is listening on port 80 (HTTP) using commands like 'netstat -an | grep :80' or 'nmap -p 80 <device_ip>'Affected if Port 80/HTTP is open and accessible on the device
-
Confirm HTTPS is not enabled or enforcedCheck if port 443 (HTTPS) is open using 'netstat -an | grep :443' or attempt to access the device via https:// URLAffected if HTTPS is not listening or redirects/falls back to HTTP
-
Inspect web traffic for cleartext transmissionUse a packet capture tool (like Wireshark or tcpdump) while authenticating or accessing sensitive pages. Filter for HTTP traffic on port 80Affected if Authentication credentials, session cookies, or personal data are visible in clear text over HTTP
-
Review web server configuration filesExamine the device's web server configuration for SSL/TLS settings. Look for directives enabling 'ssl', 'tls', or 'https'Affected if SSL/TLS is disabled or no secure protocol is configured
-
Check for secure transport enforcementAttempt to access the web interface over HTTP and observe whether the server redirects to HTTPS or rejects the connectionAffected if HTTP access is accepted without redirect to HTTPS and sensitive data can be transmitted
The device is affected if its web server accepts unencrypted HTTP connections and transmits authentication credentials, session data, or personal information in clear text without enforcing HTTPS/TLS.
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 and enforce TLS/HTTPS for all web server communications, ensuring sensitive data is encrypted in transit. Verify that the device supports encrypted protocols and configure it to use secure communication channels exclusively.
- 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-2025-64389 — 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-2025-64389 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