CVE-2025-6803
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 compressDriverFiles 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 compressDriverFiles 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-24923.
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 exists in the compressDriverFiles method of Marvell QConvergeConsole due to insufficient validation of user-supplied path parameters before file operations. An unauthenticated remote attacker can exploit this to read arbitrary files on the affected system, potentially exposing sensitive configuration, credentials, or system files with SYSTEM privileges.
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.
-
Identify if Marvell QConvergeConsole is installedSearch the system for QConvergeConsole installation directories or check for the QConvergeConsole service. Common locations may include C:\Program Files\Marvell\ or /opt/marvell/ on Linux systems. Check the Windows registry under HKLM\SOFTWARE\Marvell\QConvergeConsole if on Windows.Affected if Marvell QConvergeConsole software is found on the system
-
Determine the installed versionAccess the QConvergeConsole web interface and navigate to the About or version information page, or check the installer logs and application files for version metadata. Compare the version number to 5.5.0.85.Affected if The installed version is 5.5.0.85 or lower
-
Verify the compressDriverFiles feature is accessibleConfirm that the QConvergeConsole web application is running and the compressDriverFiles functionality is exposed. This is typically accessed via an HTTP endpoint in the management interface.Affected if The compressDriverFiles endpoint is reachable and functional
-
Check network exposure of the management interfaceReview firewall rules and network configuration to determine if the QConvergeConsole management ports (commonly HTTPS ports 8443 or 9443) are exposed to untrusted networks or the public internet.Affected if The QConvergeConsole management interface is accessible from untrusted network segments or the internet
The system is affected if Marvell QConvergeConsole version 5.5.0.85 or lower is installed with the compressDriverFiles feature exposed to network access, allowing unauthenticated attackers to potentially exploit the directory traversal vulnerability.
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 the vendor patch when available. In the interim, restrict network access to QConvergeConsole management interfaces and implement WAF rules to detect path traversal patterns in requests.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6803 — 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-6803 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