3scaleApplication · Redhat
CVE-2021-3412
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 · uneditedIt was found that all versions of 3Scale developer portal lacked brute force protections. An attacker could use this gap to bypass login controls, and access privileged information, or possibly conduct further attacks.
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 · moderate confidenceThe 3Scale developer portal in all versions lacks brute force protection mechanisms on its login functionality. This allows attackers to repeatedly attempt credential guesses without rate limiting or account lockout, potentially leading to unauthorized access to privileged information or further attack progression.
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
all versions
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
-
Confirm 3Scale developer portal is accessibleIdentify the URL of your 3Scale developer portal (typically at /login or /portal/login paths). Verify the portal is reachable from the network.Affected if The developer portal is exposed and reachable without additional authentication.
-
Check if rate limiting is configured on login endpointReview your 3Scale configuration files (typically in /etc/3scale or the APIcast configuration) and check for rate limiting rules on the login POST endpoint. Look for nginx configuration or API policy settings that limit login request frequency.Affected if No rate limiting or throttling is configured on login attempts, allowing unlimited requests.
-
Verify account lockout policy existsCheck the 3Scale admin console or configuration for account lockout settings after failed login attempts. Look for policies that temporarily or permanently disable accounts after X failed attempts.Affected if No account lockout or account temporary disable policy is configured after failed login attempts.
-
Check for CAPTCHA or anti-automation on loginInspect the login page source or form configuration to determine if CAPTCHA or similar challenge mechanisms (like reCAPTCHA, honeypot fields, or behavioral analysis) are present on the login form.Affected if No CAPTCHA or anti-automation challenge is present on the login functionality.
You are affected if you have an exposed 3Scale developer portal without rate limiting, account lockout policies, or CAPTCHA protections on the login functionality.
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 dataImplement brute force protections including rate limiting on login attempts, account lockout policies after failed attempts, and optionally CAPTCHA challenges to prevent automated login guessing.
Fix this in 3scale
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-3412 — 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-2021-3412 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