Cyber Resilience

CVE-2023-33838

Crypto Weakness in Ibm Security Verify Governance 10.0.2

Crypto Weakness
Published
29 January 2025
Modified
04 March 2025
Patch / advisory
View advisory
CVSS Score v3.1 4.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0024 15th percentile
Risk Priority 34 floored blend · peak EPSS

Summary

CVE-2023-33838 is a medium-severity Use of a One-Way Hash without a Salt (CWE-759) vulnerability in Ibm Security Verify Governance. Its CVSS base score is 4.4 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Brute Force (T1110); ranked at the 15th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to IA-5 (Authenticator Management) and SA-11 (Developer Testing and Evaluation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A04:2025 Cryptographic Failures

EU & UK References

Vulnerability Data

IBM Security Verify Governance 10.0.2 Identity Manager uses a one-way cryptographic hash against an input that should not be reversible, such as a password, but the product does not also use a salt as part of the input.

CWE(s)
CWE-759CWE-916

Related Threats

MITRE ATT&CK Enterprise Techniques

T1110 Brute Force Credential Access
Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained.
attack.mitre.org →
T1110.002 Password Cracking Credential Access
Adversaries may use password cracking to attempt to recover usable credentials, such as plaintext passwords, when credential material such as password hashes are obtained.
attack.mitre.org →
T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-22330Same product: Ibm Security Verify Governance
CVE-2023-33836Same product: Ibm Security Verify Governance
CVE-2023-35013Same product: Ibm Security Verify Governance
CVE-2023-35016Same product: Ibm Security Verify Governance
CVE-2023-35017Same product: Ibm Security Verify Governance
CVE-2023-33844Same product: Ibm Security Verify Governance
CVE-2023-35888Same product: Ibm Security Verify Governance
CVE-2023-35019Same product: Ibm Security Verify Governance
CVE-2023-33837Same product: Ibm Security Verify Governance
CVE-2025-36003Same product: Ibm Security Verify Governance

Affected Assets

ibm
security verify governance
10.0.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V11.4.2

Mitigating Controls (NIST 800-53 r5) AI

SC-13 Cryptographic Protection good match

Cryptographic protection requirements specify approved algorithms and usage that encompass salted one-way hashes for passwords.

IA-5 Authenticator Management good match

Authenticator management requires secure credential storage practices that include salted hashes.

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can identify missing salt values through code review or analysis.

SA-15 Development Process, Standards, and Tools partial match

Development standards and tools can mandate salted hashing as part of secure implementation requirements.

SC-28 Protection of Information at Rest partial match

Protection of information at rest requires cryptographic safeguards on stored password hashes, reducing exposure to offline cracking.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 full match
prevents

Secure SDLC practices mandate correct password storage with salts, eliminating this exact weakness.

PR.DS-01 mostly match
prevents

Proper cryptographic hashing for data-at-rest protection directly requires salted hashes for passwords.

PR.AA-03 partial match
prevents

Authentication policies may reference password handling but do not address storage or computational cost of hashes.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.24 Use of cryptography mostly match
prevents

Use of cryptography requires appropriate cryptographic controls including salting for password hashing.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect unsalted hashes but does not prevent their introduction.

A.5.17 Authentication information partial match
degrades

Requires secure handling of authentication information, which includes choosing strong password hashing schemes.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC processes can include password-handling rules but do not guarantee salted hashes.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate salted hashing but do not prescribe the technical detail.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid unsalted password hashes and require salting.

References