CVE-2024-22330VulnerabilityPublished 6 Jun 2025

CVE-2024-22330: IBM Security Verify Governance · Weak Password Requirements

Affects IBM Security Verify GovernanceSource CVE Database V5

Not known to be exploited · CVSS 5.9 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
IBM Security Verify Governance	Affected =10.0.2	Fixed in–

AI-suggested

Organizations should immediately review and enforce strong password policies within IBM Security Verify Governance 10.0.2, overriding default settings to require complex passwords (e.g., minimum length, character variety, and prohibiting common passwords). Implement multi-factor authentication (MFA) for all user accounts to reduce reliance on passwords alone. Conduct an audit of existing user accounts to identify and remediate weak passwords. Monitor authentication logs for unusual access patterns indicative of brute-force or credential stuffing attacks. Where possible, upgrade to a later version of the product if IBM releases patches or enhanced security configurations addressing this issue. Additionally, integrate IBM Security Verify Governance with centralized identity and access management solutions that enforce enterprise-wide password policies. Train administrators and users on the importance of strong passwords and secure credential management. Finally, implement network-level protections such as rate limiting and IP blacklisting to mitigate automated attack attempts.

Description

IBM Security Verify Governance 10.0.2 does not require that users should have strong passwords by default, which makes it easier for attackers to compromise user accounts.

Impact

For European organizations using IBM Security Verify Governance 10.0.2, this vulnerability poses a significant risk to the confidentiality of sensitive identity and access management data. Compromise of user accounts could lead to unauthorized access to governance workflows, user entitlement data, and potentially privileged accounts if weak passwords are exploited. This could facilitate insider threat scenarios, privilege escalation, or lateral movement within enterprise networks. Given the critical role of identity governance in regulatory compliance (e.g., GDPR), a breach could also result in legal and financial repercussions. The medium CVSS score reflects that exploitation is not trivial due to high attack complexity, but the lack of required authentication and user interaction lowers the barrier for attackers who can identify weak passwords. European organizations in sectors with stringent compliance requirements such as finance, healthcare, and government are particularly at risk, as identity governance solutions are integral to their security posture. The confidentiality impact could lead to exposure of personal data and access rights, undermining trust and regulatory compliance.

CWE-521Weak Password Requirements (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product does not require that users should have strong passwords.
Architecture and Design
A product's design should require adherance to an appropriate password policy. Specific password requirements depend strongly on contextual factors, but it is recommended to contain the following attributes: Enforcement of a minimum and maximum length; Restrictions against password reuse; Restrictions against using…
Architecture and Design
Consider a second authentication factor beyond the password, which prevents the password from being a single point of failure. See CWE-308 for further information.
Implementation
Consider implementing a password complexity meter to inform users when a chosen password meets the required attributes.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.1.2 (opens in a new tab)
V2.1.4 (opens in a new tab)
V2.1.3 (opens in a new tab)
Attack patterns
Dictionary-based Password Attack (opens in a new tab)
Password Brute Forcing (opens in a new tab)
Kerberoasting (opens in a new tab)
Rainbow Table Password Cracking (opens in a new tab)
Remote Services with Stolen Credentials (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

ibm.com/support/pages/node/7235779 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Jul 2025, 17:27 UTC

WeaknessesCWE-521

Technical details

References

Community reviews

Related threats