CVE-2020-17388
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 · uneditedThis 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 Tomcat configuration file. The issue results from the lack of proper restriction to the Tomcat admin console. An attacker can leverage this vulnerability to execute code in the context of SYSTEM. Was ZDI-CAN-10799.
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 · moderate confidenceThis vulnerability in Marvell QConvergeConsole 5.5.0.64 allows remote authenticated attackers to bypass authentication and execute arbitrary code as SYSTEM. The flaw exists in the Tomcat configuration where the admin console lacks proper access restrictions, enabling attackers to leverage the unprotected Tomcat management interface to deploy malicious code.
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.00.73CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify QConvergeConsole versionLocate the installed QConvergeConsole version on the system, typically found in the application directory or via system inventory tools. Common locations include the installation folder or Windows Programs and Features.Affected if The installed version is 5.5.0.64 or any version prior to 5.5.00.73.
-
Locate Tomcat management interfaceIdentify the HTTP port used by QConvergeConsole's embedded Tomcat server. This is typically configured in server.xml or similar Tomcat configuration files within the QConvergeConsole installation directory.Affected if The Tomcat management interface port is accessible on the network.
-
Test Tomcat manager access without credentialsAttempt to access the Tomcat manager application (typically at /manager/html) on the QConvergeConsole server using a web browser or curl command, without providing any authentication credentials.Affected if The Tomcat manager interface loads or responds without requiring authentication.
-
Verify Tomcat configuration for access restrictionsExamine the Tomcat configuration files (such as conf/tomcat-users.xml and the web.xml for the manager application) in the QConvergeConsole installation directory to determine if role-based access control is properly configured and enforced.Affected if The Tomcat configuration lacks proper authentication enforcement or allows unrestricted access to management interfaces.
The environment is affected if QConvergeConsole version is below 5.5.00.73 AND the Tomcat management interface is accessible without authentication, allowing an attacker to deploy malicious code.
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 data5.5.00.73
Restrict access to the Tomcat admin console by implementing proper authentication, enforcing role-based access controls, and applying network segmentation to limit exposure. If a vendor patch is available, apply it immediately.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-17388 — 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-2020-17388 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