Mirror Registry For Red Hat OpenshiftApplication · Redhat
CVE-2025-14243
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 the OpenShift Mirror Registry. This vulnerability allows an unauthenticated, remote attacker to enumerate valid usernames and email addresses via different error messages during authentication failures and account creation.
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 confidenceThe OpenShift Mirror Registry returns distinct error messages for authentication failures and account creation events that reveal whether specific usernames or email addresses are valid in the system. An unauthenticated remote attacker can exploit this by sending login or registration requests with various username/email combinations and analyzing the different error responses to enumerate valid accounts.
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
Mirror Registry For Red Hat OpenshiftApplication
all versions= 2.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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Identify Mirror Registry installationLocate the OpenShift Mirror Registry deployment in your environment - check for pods, services, or containers running the mirror-registry imageAffected if Mirror Registry is deployed and accessible externally or internally
-
Test authentication with non-existent usernameAttempt to authenticate with a username that does not exist in the system; capture the exact error message returnedAffected if The error message specifically indicates 'user not found', 'user does not exist', or similar that confirms the username is invalid
-
Test authentication with existing username but wrong passwordAttempt to authenticate with a valid username but incorrect password; capture the exact error message returnedAffected if The error message specifically indicates 'invalid password', 'incorrect password', or similar that confirms the username exists but password is wrong
-
Compare error message contentReview both error messages from steps 2 and 3 - check if they differ in a way that reveals whether the username is validAffected if The messages are different - one reveals user existence while the other confirms user exists but authentication failed
-
Test account creation or password reset flowIf available, attempt to create a new account or trigger password reset using various email addresses or usernames; observe if responses differ based on account existenceAffected if Error messages differ between existing and non-existing accounts, revealing valid usernames or emails
Your environment is affected if authentication attempts return different error messages that allow an attacker to determine whether a username or email address exists in the system.
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 dataStandardize all authentication and account creation error messages to return generic responses (e.g., 'Invalid credentials' or 'Account creation failed') regardless of whether the username or email exists, preventing user enumeration.
Fix this in Mirror Registry For Red Hat Openshift
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14243 — 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-2025-14243 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