Credential brute force via missing CAPTCHA enforcement
Published Mar 16, 2022 · Updated Oct 4, 2024
Improper authentication-attempt restriction in Atlassian FishEye and Crucible before 4.8.9 allows remote attackers to brute-force credentials. Affected REST resources accept authentication attempts without checking whether the user exceeded the failed-login limit and must solve a CAPTCHA. No account is required to submit guesses, and the bypass removes the CAPTCHA barrier after the configured limit.
Summary
What happened
Improper authentication-attempt restriction in Atlassian FishEye and Crucible before 4.8.9 allows remote attackers to brute-force credentials. Affected REST resources accept authentication attempts without checking whether the user exceeded the failed-login limit and must solve a CAPTCHA. No account is required to submit guesses, and the bypass removes the CAPTCHA barrier after the configured limit.
The record
- CVE
- CVE-2021-43958
- Published
- Mar 16, 2022
- Updated
- Oct 4, 2024
- Vendor
- Atlassian
- Product
- FishEye
- Classifications
- CWE-307, T1110
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 16, 2022CVE publishedPublication date reported by the CVE source.
- Oct 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <4.8.9
- Affected versionversion=unspecified <4.8.9
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo