Credential brute force via inadequate account lockout
Published Jul 7, 2021 · Updated Sep 17, 2024
Guardium Data Encryption 4.0.0.4 has an authentication weakness that lets remote attackers brute-force account credentials over the network. Its account lockout setting permits repeated credential attempts instead of enforcing an effective threshold, allowing password guessing against exposed login services. The attack is unauthenticated but requires network reachability to the GDE service; successful guessing compromises the targeted account and its accessible encrypted-data functions.
Summary
What happened
Guardium Data Encryption 4.0.0.4 has an authentication weakness that lets remote attackers brute-force account credentials over the network. Its account lockout setting permits repeated credential attempts instead of enforcing an effective threshold, allowing password guessing against exposed login services. The attack is unauthenticated but requires network reachability to the GDE service; successful guessing compromises the targeted account and its accessible encrypted-data functions.
The record
- CVE
- CVE-2021-20415
- Published
- Jul 7, 2021
- Updated
- Sep 17, 2024
- Vendor
- IBM
- Product
- Guardium Data Encryption
- Classifications
- CWE-307, T1110
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 7, 2021CVE publishedPublication date reported by the CVE source.
- Sep 17, 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=4.0.0.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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