CrucibleApplication · Atlassian
CVE-2021-43958
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 · uneditedVarious rest resources in Fisheye and Crucible before version 4.8.9 allowed remote attackers to brute force user login credentials as rest resources did not check if users were beyond their max failed login limits and therefore required solving a CAPTCHA in addition to providing user credentials for authentication via a improper restriction of excess authentication attempts vulnerability.
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 REST API endpoints in Fisheye and Crucible failed to enforce max failed login limits and CAPTCHA challenges that the web interface enforced. Attackers could use these unrestricted REST endpoints to brute force user credentials without triggering account lockout or CAPTCHA, making credential attacks trivial.
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
CrucibleApplication
< 4.8.9
FisheyeApplication
< 4.8.9CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 the installed productDetermine whether Atlassian Fisheye or Atlassian Crucible is running in your environment, or if both are present. Check the product name visible in the admin interface or service details.Affected if Either product is present in the environment
-
Check the installed version of FisheyeLocate the Fisheye version through the admin interface under 'System' > 'General' or by checking the version file in the Fisheye installation directory. Note the exact version number.Affected if The version is lower than 4.8.9
-
Check the installed version of CrucibleLocate the Crucible version through the admin interface under 'System' > 'General' or by checking the version file in the Crucible installation directory. Note the exact version number.Affected if The version is lower than 4.8.9
A user is affected if either Fisheye or Crucible is installed at a version lower than 4.8.9, as these versions lack the authentication controls on REST API endpoints that the web interface enforces.
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.
dbcve · scoped4.8.9
Upgrade Fisheye and Crucible to version 4.8.9 or later, which applies the same authentication controls to REST resources as the web interface.
Fisheye/Crucible 4.8.9 or later
- Back up your Fisheye/Crucible data and configuration files before proceeding with the upgrade
- Download Fisheye or Crucible version 4.8.9 or later from the official Atlassian download center
- Stop the running Fisheye or Crucible service
- Install the upgraded version following standard Atlassian installation procedures
- Restart the Fisheye or Crucible service
- Verify the application is running correctly and that the login mechanism now properly enforces max failed login limits and CAPTCHA requirements
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Crucible
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-43958 — 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-43958 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