CVE-2024-31874VulnerabilityPublished 10 Apr 2024Updated 3 Nov 2025

CVE-2024-31874: IBM Security Verify Access Appliance · Use of Uninitialized Variable

Affects IBM Security Verify Access ApplianceSource CVE Database V5

Not known to be exploited · CVSS 6.2 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.2Medium

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

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

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

Attack Vector: Local
Attack Complexity: Low
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: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
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 10 Apr 2024
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-25.

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
Ibmibm/security-verify-access-appliance`pkg:rpm/ibm/security-verify-access-appliance`Other threats	Affected =10.0.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately restrict local access to IBM Security Verify Access Appliances to trusted administrators only, employing strict physical and network access controls. Monitor and audit local access logs for any suspicious activity that could indicate attempts to exploit this vulnerability. Since no patches are currently available, implement compensating controls such as isolating the appliance in a secure network segment with limited user access. Prepare to apply IBM's official patches or updates as soon as they are released. Conduct thorough internal security reviews and penetration tests focusing on local privilege escalation and insider threat scenarios. Additionally, ensure that backup and recovery procedures are in place to quickly restore appliance functionality in case of a denial of service. Consider deploying endpoint detection and response (EDR) solutions on systems with local access to detect anomalous behavior. Finally, educate administrators about the risks of local exploitation and enforce the principle of least privilege.

Description

IBM Security Verify Access Appliance 10.0.0 through 10.0.7 uses uninitialized variables when deploying that could allow a local user to cause a denial of service. IBM X-Force ID: 287318.

Impact

For European organizations, this vulnerability could lead to service disruptions in identity and access management systems, potentially affecting user authentication and access controls. Since the appliance is used to secure access to critical applications and data, a denial of service could interrupt business continuity, especially in sectors like finance, healthcare, and government where IBM appliances are commonly deployed. The confidentiality impact suggests that sensitive information might be exposed, which could lead to data leakage or compliance issues under GDPR. The requirement for local access reduces the likelihood of remote exploitation but increases risk from insider threats or attackers who have already compromised internal systems. Disruptions in authentication services could also affect federated identity systems and single sign-on (SSO) environments, amplifying the operational impact. Organizations relying heavily on IBM Security Verify Access Appliance for secure access management should consider this vulnerability a significant risk to their identity infrastructure.

CWE-457Use of Uninitialized Variable (opens in a new tab)
Variant weaknessLikelihood of exploit: High
The code uses a variable that has not been initialized, leading to unpredictable or unintended results.
Implementation · Attack Surface Reduction
Ensure that critical variables are initialized before first use.
Build and Compilation · Compilation or Build Hardening
Most compilers will complain about the use of uninitialized variables if warnings are turned on.
Implementation · Operation
When using a language that does not require explicit declaration of variables, run or compile the software in a mode that reports undeclared or unknown variables. This may indicate the presence of a typographic error in the variable's name.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2025, 00:00 UTC

WeaknessesCWE-457

Technical details

References

Community reviews

Related threats