3scaleApplication · Redhat
CVE-2020-25634
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 Red Hat 3scale’s API docs URL, where it is accessible without credentials. This flaw allows an attacker to view sensitive information or modify service APIs. Versions before 3scale-2.10.0-ER1 are affected.
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 confidenceRed Hat 3scale API documentation endpoints are accessible without requiring authentication, allowing unauthenticated attackers to view sensitive API documentation and potentially modify service API configurations. This authorization bypass affects versions prior to 3scale-2.10.0-ER1.
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
3scaleApplication
< 2.10.0= 2.10.0
3scale Api ManagementApplication
= 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 installed 3scale versionCheck the 3scale version by reviewing the product version file, container image tags, or the admin portal footer. Common locations: /opt/3scale/version file, Docker/Kubernetes image tags, or the System > Overview page in the admin dashboard.Affected if The installed version is less than 2.10.0-ER1, equals 2.10.0, or is version 2.0 of 3scale API Management.
-
Verify docs endpoint accessibilityAttempt to access common 3scale API documentation URLs without authentication. Common endpoints include: /docs, /api/docs, /p/admin/docs, /swagger.json, /api-docs, or similar paths under the main 3scale domain.Affected if The documentation pages load or return HTTP 200 without requiring login credentials.
-
Check admin portal docs exposureAttempt to access the /p/admin/ path or admin documentation routes without being logged in. These should require authentication but the vulnerability allows bypass.Affected if Admin documentation or developer portal content loads without authentication prompt.
-
Review proxy/gateway configurationInspect the API gateway or reverse proxy configuration (e.g., Nginx, Envoy) for rules controlling access to documentation endpoints. Look for location blocks or routes handling /docs paths.Affected if No authentication layer is configured for documentation routes, or docs are explicitly marked as publicly accessible.
A user is affected if their 3scale version falls within the vulnerable range (< 2.10.0-ER1 or = 2.10.0 for 3scale, or = 2.0 for API Management) AND the API documentation endpoints are accessible without authentication.
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 data2.10.0
Upgrade to 3scale-2.10.0-ER1 or later which includes proper authentication enforcement for API documentation URLs. Alternatively, implement access controls at the gateway or proxy level to restrict unauthenticated access to docs endpoints.
Fix this in 3scale
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-2020-25634 — 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-25634 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