CVE-2025-6799
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 · uneditedMarvell QConvergeConsole getFileUploadBytes Directory Traversal Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of Marvell QConvergeConsole. Authentication is not required to exploit this vulnerability. The specific flaw exists within the implementation of the getFileUploadBytes method. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to disclose information in the context of SYSTEM. Was ZDI-CAN-24919.
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 confidenceA directory traversal vulnerability in the getFileUploadBytes method of Marvell QConvergeConsole allows unauthenticated remote attackers to read arbitrary files on the affected system by supplying path traversal sequences (e.g., ../../) in user input. The lack of proper path validation before file operations, combined with execution as SYSTEM context, enables disclosure of sensitive system files beyond the web root.
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<= 5.5.0.85CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/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.
-
Confirm QConvergeConsole installationCheck for QConvergeConsole service or web interface: look for process 'QConvergeConsole' in task list, or check for port 8443/8080 listeners. On Windows, also check installed programs list.Affected if QConvergeConsole is installed and running on the system
-
Identify installed versionCheck the version of QConvergeConsole. Common locations: check the application's About/Help section, or look for version file in installation directory (typically C:\Program Files\Marvell\QConvergeConsole\ or /opt/marvell/qconvergeconsole/). The version may be displayed in the login page footer or in registry keys on Windows.Affected if Installed version is 5.5.0.85 or lower, or if version cannot be determined but the product is present
-
Assess network exposureDetermine if the QConvergeConsole web interface (ports 8443, 8080, or configured port) is accessible from untrusted networks. Check firewall rules and binding addresses in server configuration.Affected if Management interface is reachable from outside trusted networks or directly from the internet
-
Examine web server logs for traversal attemptsReview QConvergeConsole access logs for patterns containing '../', '..\', or unusual file path requests. Log locations vary by installation but are typically in a 'logs' or 'Tomcat/logs' subdirectory within the QConvergeConsole folder.Affected if Recent log entries contain directory traversal patterns targeting sensitive system paths
-
Check for unauthorized file accessReview system for any recently accessed files outside the expected web root, particularly sensitive files like C:\Windows\System32\config\SAM, C:\Windows\repair\sam, or /etc/shadow on Linux systems.Affected if File access logs or system monitoring shows QConvergeConsole process accessing files outside its intended web root directory
System is affected if QConvergeConsole version 5.5.0.85 or lower is installed and its management interface is network-accessible, since the unauthenticated directory traversal vulnerability can be exploited to read arbitrary files.
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 dataApply vendor-supplied patch when available; until then, restrict network access to QConvergeConsole management interfaces and deploy WAF rules to block directory traversal patterns in HTTP requests.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6799 — 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-6799 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