CVE-2020-10590
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 · uneditedReplicated Classic 2.x versions have an improperly secured API that exposes sensitive data from the Replicated Admin Console configuration. An attacker with network access to the Admin Console port (8800) on the Replicated Classic server could retrieve the TLS Keypair (Cert and Key) used to configure the Admin Console.
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 confidenceReplicated Classic 2.x has an improperly secured API on port 8800 (Admin Console) that exposes TLS certificate and private key pairs used for the Admin Console. An attacker with network access to port 8800 can retrieve these sensitive credentials without authentication.
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>= 2.10.0, <= 2.32.3>= 2.33.0, <= 2.36.0>= 2.37.0, <= 2.37.1>= 2.38.0, <= 2.38.5>= 2.39.0, <= 2.39.3>= 2.40.0, <= 2.40.3>= 2.42.0, <= 2.42.3= 2.41.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Replicated Classic is installedIdentify if the host is running Replicated Classic by checking for Replicated processes or the presence of /var/lib/replicated directoryAffected if Replicated Classic is installed and running on the host
-
Verify port 8800 is accessibleRun 'netstat -tlnp | grep 8800' or 'ss -tlnp | grep 8800' to check if port 8800 is listeningAffected if Port 8800 is open and listening on the Admin Console
-
Check installed version of Replicated ClassicRun 'replicatedctl version' or check /var/lib/replicated/app.json for the version string, then compare against affected ranges: 2.10.0-2.32.3, 2.33.0-2.36.0, 2.37.0-2.37.1, 2.38.0-2.38.5, 2.39.0-2.39.3, 2.40.0-2.40.3, 2.41.0, 2.42.0-2.42.3Affected if The installed version falls within any of the affected version ranges
-
Test unauthenticated API access on port 8800Run 'curl -k https://localhost:8800/v1/certificate' or attempt the same request from a remote host with network access to port 8800 without providing credentialsAffected if The API responds with TLS certificate or private key data without requiring authentication
A host is affected if it runs a Replicated Classic version within the affected ranges and has port 8800 accessible, allowing unauthenticated retrieval of TLS credentials from the API endpoint.
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 dataRestrict network access to port 8800 to trusted networks only, and immediately rotate any exposed TLS certificates and private keys.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10590 — 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-10590 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