CVE intelligence and bounded remediation

CVE-2021-42718 — Information Disclosure in API in Replicated Replicated Classic security vulnerability

Medium CVSS 4.9

Information Disclosure in API in Replicated Replicated Classic versions prior to 2.53.1 on all platforms allows authenticated users with Admin Console access to retrieve sensitive data, including application secrets, via accessing container definitions with environment variables through the Admin Console API on port 8800. This CVE was originally reserved in 2021 and later publicly disclosed by Replicated on their website on 21 October 2021. However, it mistakenly remained in the Reserved But Public (RBP) status with the CVE Numbering Authority (CNA). Please note that this product reached its end of life on 31 December 2024. Publishing this CVE with the CNA was required to comply with CNA rules, despite the fact that the issue was disclosed and fixed four years ago, and the affected product is no longer supported as of 2024. Summary of VulnerabilityThis advisory discloses a low severity security vulnerability in the versions of Replicated Classic listed above (“Affected Replicated Classic Versions”) DescriptionReplicated Classic versions prior to 2.53.1 have an authenticated API from the Replicated Admin Console that may expose sensitive data including application secrets, dependin…

Severity
Medium
CVSS
4.9 (3.1)
Published
2025-01-23
CISA KEV
Not currently listed
Ecosystem
software/application
Weaknesses
CWE-922

Affected products

No browser-safe affected-product rows are available.

Matched remediation archetype

Information disclosure and sensitive data exposure

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Trace sensitive data through responses, errors, logs, metrics, traces, caches, exports, files, backups, and client bundles.
  • Identify affected subjects, tenants, retention windows, access controls, and downstream copies without opening unnecessary sensitive records.
  • Review metadata, timing, status, length, and existence signals as well as direct content disclosure.

Remediate safely

  • Minimize collection and output, apply field-level authorization and redaction at a centralized boundary, and return generic external errors.
  • Remove secrets and sensitive data from logs, artifacts, URLs, caches, and client-side bundles; rotate credentials that may have been exposed.
  • Update the affected component and add synthetic-data tests for response, error, observability, and export paths.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.