CVE-2024-39178
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 · uneditedMyPower vc8100 V100R001C00B030 was discovered to contain an arbitrary file read vulnerability via the component /tcpdump/tcpdump.php?menu_uuid.
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 confidenceMyPower vc8100 V100R001C00B030 contains an arbitrary file read vulnerability in /tcpdump/tcpdump.php via the menu_uuid parameter. An unauthenticated attacker can potentially read sensitive files from the server filesystem by manipulating this parameter.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 MyPower vc8100 installation and versionLocate the MyPower vc8100 device or software on your network and retrieve its firmware/software version information, typically found in the system info page, CLI 'show version' command, or management interface about section.Affected if The installed version matches or is within the V100R001C00B030 release line (e.g., V100R001C00B030 or related versions in the V100R001C00Bx range).
-
Verify tcpdump.php endpoint existsAttempt to access the URI /tcpdump/tcpdump.php on the MyPower vc8100 management interface or web server. This may be at a path like https://<device-ip>/tcpdump/tcpdump.php or similar depending on your deployment.Affected if The endpoint responds with any HTTP status code (200, 401, 403, 404, etc.), indicating the file exists and is reachable over the network.
-
Confirm endpoint accessibility without authenticationSend an HTTP GET request to the tcpdump.php endpoint without providing any authentication credentials or session cookies.Affected if The endpoint returns a response without requiring login, Basic Auth, or other authentication mechanisms.
-
Test for path traversal via menu_uuid parameterSend an HTTP GET request to tcpdump.php with a manipulated menu_uuid parameter containing path traversal sequences, such as menu_uuid=../../../../etc/passwd or similar, and observe if file contents are returned in the response.Affected if The server returns file contents from the filesystem (such as /etc/passwd, configuration files, or other system files) in the response body.
If your MyPower vc8100 is running version V100R001C00B030 or related versions, the /tcpdump/tcpdump.php endpoint is accessible, and the menu_uuid parameter allows reading arbitrary files, then your environment is affected by this CVE.
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 access to the tcpdump.php endpoint, implement strict input validation on the menu_uuid parameter to prevent path traversal, and disable or remove the tcpdump functionality if not required. Consider network segmentation to limit exposure.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-39178 — 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-39178 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