QconvergeconsoleApplication · Marvell

CVE-2020-17389

HIGH · 8.8 CVSS v3.1 Published 2020-08-25
Fix available
A fix is available. Upgrade to 5.5.00.73 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 execute arbitrary code on affected installations of Marvell QConvergeConsole 5.5.0.64. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed. The specific flaw exists within the decryptFile method of the GWTTestServiceImpl 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 execute code in the context of SYSTEM. Was ZDI-CAN-10502.

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

Path traversal vulnerability in Marvell QConvergeConsole 5.5.0.64's GWTTestServiceImpl class (decryptFile method) allows remote authenticated attackers to supply arbitrary file paths for file operations. While authentication is required, the authentication mechanism itself can be bypassed, enabling arbitrary code execution in SYSTEM context.

MitigationImplement strict path validation to prevent directory traversal attacks (e.g., canonicalize paths and verify they fall within allowed directories), fix the authentication bypass, and apply least-privilege principles to restrict SYSTEM-level access.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 QConvergeConsole installation and version
    Locate the QConvergeConsole installation directory and look for version information in about dialog, installer logs, or version file (commonly in the installation root or help/about section). Alternatively, query the web interface login page or check the WAR file manifest if accessible.
    Affected if Installed version is 5.5.0.64 or any version prior to 5.5.00.73
  2. Verify GWTTestServiceImpl endpoint is accessible
    Check if the GWTTestServiceImpl service endpoint is exposed by attempting to access the URL pattern typically used by GWT services (such as /GWTTestServiceImpl or searching for GWT RPC endpoints in the web.xml). Use a web proxy or curl to probe for the service endpoint.
    Affected if The GWTTestServiceImpl service is reachable over the network without restrictions
  3. Confirm decryptFile method exists and is enabled
    Inspect the deployed web application WAR file or decompile the GWTTestServiceImpl class to verify the decryptFile method is present. Alternatively, examine HTTP responses when interacting with the GWT service to confirm the method is exposed.
    Affected if The decryptFile method is present and callable through the web service interface
  4. Check if authentication can be bypassed
    Test the authentication mechanism by accessing protected resources without valid credentials or by analyzing the authentication logic for known bypass vulnerabilities (such as null session or default credential usage). Review whether the authentication bypass condition (related to the specific vulnerability) can be triggered.
    Affected if Unauthenticated or trivially authenticated access to the vulnerable service is possible
  5. Verify SYSTEM-level execution context
    Confirm the QConvergeConsole service runs under the SYSTEM or highly privileged account by examining the service configuration in Windows Services or Unix process listings.
    Affected if The service runs with SYSTEM or administrator-level privileges, allowing the exploited code to execute at high privilege

A user is affected if QConvergeConsole version is below 5.5.00.73, the GWTTestServiceImpl with decryptFile method is exposed, and either valid authentication or an authentication bypass is present, with the service running at SYSTEM privilege level.

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

Implement strict path validation to prevent directory traversal attacks (e.g., canonicalize paths and verify they fall within allowed directories), fix the authentication bypass, and apply least-privilege principles to restrict SYSTEM-level access.

Fix this in Qconvergeconsole Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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 locally
dbcve dependency scanner

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