Openshift Container PlatformApplication · Redhat
CVE-2020-10712
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 · uneditedA flaw was found in OpenShift Container Platform version 4.1 and later. Sensitive information was found to be logged by the image registry operator allowing an attacker able to gain access to those logs, to read and write to the storage backing the internal image registry. The highest threat from this vulnerability is to data integrity.
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 confidenceIn OpenShift Container Platform 4.1+, the image registry operator logs sensitive information (likely storage credentials or access tokens) that can be retrieved by an attacker with log access. This exposed authentication material grants read/write access to the storage backend backing the internal image registry, enabling data integrity compromise.
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
Openshift Container PlatformApplication
<= 4.1CVSS 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
- Low
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/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 OpenShift Container Platform versionRun 'oc get clusterversion version' or check the OCP version via 'oc version' to identify the installed versionAffected if The version is 4.1 or lower (4.1.x, any 4.0.x, or earlier)
-
Verify image registry operator is deployedRun 'oc get clusteroperator image-registry' to confirm the image registry operator is running and its statusAffected if The image registry operator exists and is in a Available state (meaning the internal registry is configured)
-
Examine image registry operator logs for credentialsRun 'oc logs -n openshift-image-registry deployment/image-registry-operator' to retrieve operator logs, then search for patterns resembling AWS keys, Azure storage keys, GCS tokens, or base64-encoded secretsAffected if Any storage credentials, access tokens, or secret values appear in plain text within the operator logs
-
Check for exposed credentials in audit logsReview cluster audit logs (if accessible) or centralized logging for entries containing the image-registry-operator pod that show authentication materialAffected if Storage backend credentials are visible in log entries associated with the registry operator
A user is affected if they run OpenShift Container Platform version 4.1 or lower with the internal image registry operator enabled, and any credentials for the registry storage backend appear in the operator logs.
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 dataRotate any exposed credentials immediately, disable or secure registry operator logging to prevent credential exposure, and apply patches or updates that address the improper credential handling in the image registry operator.
Fix this in Openshift Container Platform
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10712 — 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-10712 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