CVE-2025-6801
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 saveNICParamsToFile Directory Traversal Arbitrary File Write Vulnerability. This vulnerability allows remote attackers to create arbitrary files on affected installations of Marvell QConvergeConsole. Authentication is not required to exploit this vulnerability. The specific flaw exists within the implementation of the saveNICParamsToFile 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 write files in the context of SYSTEM. Was ZDI-CAN-24921.
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 confidenceThis is a directory traversal vulnerability in Marvell QConvergeConsole's saveNICParamsToFile method that allows unauthenticated remote attackers to write arbitrary files to the filesystem. The flaw stems from insufficient validation of user-supplied paths before file operations, enabling attackers to write 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 installationLocate QConvergeConsole installation directory - typical paths include C:\Program Files\Marvell\QConvergeConsole or /opt/marvell/qconvergeconsole. Check for the presence of qcc.jar or qconvergeconsole executable.Affected if QConvergeConsole is not installed on the system.
-
Identify installed versionCheck the version of QConvergeConsole by examining the qcc.jar manifest, version.txt in the installation directory, or the application GUI 'About' section. Compare against the affected range: <= 5.5.0.85Affected if Installed version is 5.5.0.85 or lower.
-
Verify web service is runningCheck if the QConvergeConsole web interface is active by accessing the default port (8443 or 8080) via browser or curl command: curl -k https://<host>:8443/ or http://<host>:8080/Affected if The web interface returns a response (indicating the service is running and the attack surface is present).
-
Assess network exposureReview firewall rules and network configuration to determine if the QConvergeConsole web port (typically 8443/8080) is accessible from untrusted networks or the public internet. Use netstat or firewall-cmd to list open ports and their source restrictions.Affected if The web interface port is open to untrusted networks or the internet without proper access controls.
The environment is affected if QConvergeConsole version 5.5.0.85 or lower is installed with its web service exposed to network access, enabling unauthenticated attackers to exploit the directory traversal in saveNICParamsToFile.
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 patch when available. Until then, restrict network access to QConvergeConsole and implement network segmentation to limit exposure.
- 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-6801 — 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-6801 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