IBM Security Guardium Data Encryption (GDE) 3.0.0.2 does not require that users should have strong passwords by default, which makes it easi
IBM Security Guardium Data Encryption (GDE) 3.0.0.2 does not require that users should have strong passwords by default, which makes it easier for attackers to compromise user accounts. IBM X-Force ID: 171929.
- Published
- Aug 26, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.8% · 56th percentile
- CWE
- CWE-521
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
CNA vs NVD score
- NVD
- 7.5
- CNA · ibm
- 7.4
- 0.1 point gap
CVSS:3.0/PR:N/I:N/AV:N/S:C/AC:L/UI:R/A:N/C:H/E:U/RC:C/RL:O
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| ibm | guardium data encryption | cpe:2.3:a:ibm:guardium_data_encryption |
| ibm | guardium for cloud key management | cpe:2.3:a:ibm:guardium_for_cloud_key_management |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- ibm guardium data encryption3.0.0.2
- ibm guardium for cloud key managementbefore 1.7.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (ibm). Independent of NVD's CPE analysis and usually ahead of it.
IBM Security Guardium Data Encryption
- 3.0.0.2affected
Same product
ibm: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-4694IBM Security Guardium Data Encryption (GDE) 3.0.0.2 contains hard-coded credentials, such as a password or cryptographic key, which it uses 39Monitor
- CVE-2019-4713IBM Security Guardium Data Encryption (GDE) 3.0.0.2 could allow a remote authenticated attacker to execute arbitrary commands on the system.36Monitor
- CVE-2021-39022IBM Guardium Data Encryption (GDE) 4.0.0.0 and 5.0.0.0 saves user-provided information into a Comma-Separated Value (CSV) file, but it does 35Monitor
- CVE-2021-20378IBM Guardium Data Encryption (GDE) 3.0.0.2 and 4.0.0.4 does not invalidate session after logout which could allow an authenticated user to i35Monitor
- CVE-2021-39023IBM Guardium Data Encryption (GDE) 4.0.0 and 5.0.0 could allow a remote attacker to obtain sensitive information when a detailed technical e30Monitor
- CVE-2021-20474IBM Guardium Data Encryption (GDE) 3.0.0.2 and 4.0.0.4 does not perform any authentication for functionality that requires a provable user i30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-521 · Weak Password RequirementsCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Brute ForceCAPEC-112High
- Dictionary-based Password AttackCAPEC-16likelihood: Medium · High
- Password Brute ForcingCAPEC-49likelihood: Medium · High
- KerberoastingCAPEC-509High
- Rainbow Table Password CrackingCAPEC-55likelihood: Medium · Medium
- Remote Services with Stolen CredentialsCAPEC-555Very High
- Windows Admin Shares with Stolen CredentialsCAPEC-561
- Password SprayingCAPEC-565likelihood: High · High
ATT&CK techniques
- Remote ServicesT1021
- Remote Services:SMB/Windows Admin SharesT1021.002
- Valid Accounts:Default AccountsT1078.001
- Brute ForceT1110
- Brute Force:Password GuessingT1110.001
- Brute Force:Password CrackingT1110.002
- Brute Force:Password SprayingT1110.003
- Email Collection:Remote Email CollectionT1114.002
- External Remote ServicesT1133
- Steal or Forge Kerberos Tickets:KerberoastingT1558.003
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.