QconvergeconsoleApplication · Marvell

CVE-2020-15641

HIGH · 7.5 CVSS v3.1 Published 2020-08-25
Fix available
A fix is available. Upgrade to 5.5.00.73 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
This vulnerability allows remote attackers to disclose sensitive information on affected installations of Marvell QConvergeConsole 5.5.0.64. Authentication is not required to exploit this vulnerability. The specific flaw exists within the getFileUploadBytes method of the FlashValidatorServiceImpl class. 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 stored credentials, leading to further compromise. Was ZDI-CAN-10499.

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 confidence

This is an unauthenticated path traversal vulnerability in Marvell QConvergeConsole 5.5.0.64. The getFileUploadBytes method in FlashValidatorServiceImpl class lacks proper validation of user-supplied paths before file operations, allowing remote attackers to read arbitrary files on the system including stored credentials.

MitigationApply vendor patch when available. As an interim control, deploy WAF rules to block path traversal patterns (../, ..\) in request parameters, and restrict network access to the QConvergeConsole interface.

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
QconvergeconsoleApplication
Affected:< 5.5.00.73

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Marvell QConvergeConsole is installed
    Check for QConvergeConsole web interface by accessing the application URL (commonly port 8443 or 8080). Look for the QConvergeConsole login page or check running services on the system that match QConvergeConsole ports.
    Affected if The application is accessible on the network and presents a QConvergeConsole login interface.
  2. Determine the installed QConvergeConsole version
    Log into the QConvergeConsole admin interface and navigate to the About or System Information section to view the version number. Alternatively, check the installation directory for version information in configuration files or the application itself.
    Affected if The version displayed is less than 5.5.00.73 (for example, 5.5.0.64 or any version in the 5.5.0.x range before 5.5.00.73).
  3. Verify the FlashValidatorServiceImpl endpoint is exposed
    Attempt to access or probe the FlashValidatorServiceImpl service endpoint. This is typically exposed via the web interface under paths related to flash validation or file upload functionality. Check web server logs or application mappings for this service path.
    Affected if The FlashValidatorServiceImpl endpoint is accessible without authentication and accepts file-related requests.
  4. Confirm the system is reachable over the network
    Verify that the QConvergeConsole web interface is bound to a network-accessible IP address (not localhost only) and that firewall rules allow access to the management ports from untrusted networks.
    Affected if The QConvergeConsole management interface is reachable from networks that should not have access.

A user is affected if Marvell QConvergeConsole is running with a version lower than 5.5.00.73 and the FlashValidatorServiceImpl endpoint is network-accessible, allowing unauthenticated path traversal attacks to read arbitrary files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 5.5.00.73 or later
Fixed in 5.5.00.73
Interim mitigation

Apply vendor patch when available. As an interim control, deploy WAF rules to block path traversal patterns (../, ..\) in request parameters, and restrict network access to the QConvergeConsole interface.

Fix this in Qconvergeconsole Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,480
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,568.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-15641 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-15641 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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