CVE-2024-35294
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 · uneditedAn unauthenticated remote attacker may use the devices traffic capture without authentication to grab plaintext administrative credentials.
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 vulnerability allows unauthenticated remote attackers to access the device's traffic capture functionality without any authentication. Since the traffic capture includes plaintext administrative credentials being transmitted, an attacker can intercept these credentials by capturing network traffic.
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
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 if traffic capture functionality existsLocate the traffic capture or packet capture feature in your device's administration interface, CLI commands, or documentation. Common locations include: Network Diagnostics, Packet Capture, Sniffer, or Traffic Monitoring sections.Affected if The device has a built-in traffic capture feature that can be enabled or accessed by users.
-
Check if traffic capture requires authenticationAccess the traffic capture feature without providing any credentials or session token. Attempt to start, stop, or download a capture while logged out or in an unauthenticated browser session.Affected if The traffic capture feature can be accessed or manipulated without being logged in or without providing valid credentials.
-
Verify if captured traffic contains plaintext credentialsStart a traffic capture session, perform a login to the administrative interface, then examine the captured packets or saved capture file. Search for plaintext username and password strings in HTTP, Telnet, or other unencrypted protocol data within the capture.Affected if Administrative usernames and passwords appear in cleartext within the captured network traffic.
-
Inspect credential transmission protocolUse a packet sniffer or view the traffic capture while logging into the administrative interface. Check whether the login request uses HTTP (port 80) instead of HTTPS, or uses Telnet, FTP, or other unencrypted protocols.Affected if Administrative credentials are transmitted over unencrypted protocols (HTTP, Telnet, FTP) rather than encrypted ones (HTTPS, SSH).
You are affected if your device has a traffic capture feature that can be accessed without authentication AND captures or transmits administrative credentials in plaintext.
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 dataImplement authentication enforcement on the traffic capture feature and ensure administrative credentials are transmitted using encrypted protocols rather than plaintext.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35294 — 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-35294 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