CVE-2024-35137VulnerabilityPublished 28 Jun 2024Updated 3 Nov 2025

CVE-2024-35137: IBM Security Verify Access Docker · Empty Password in Configuration File

Affects IBM Security Verify Access DockerSource CVE Database V5

Not known to be exploited · CVSS 6.2 Medium.

Data as of 26 Oct 2026, 06:26 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 16% 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 28 Jun 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-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 Access Docker	Affected =10.0.0.0	Fixed in–

AI-suggested

European organizations should implement strict local access controls to limit who can access hosts running IBM Security Verify Access Docker containers. This includes enforcing least privilege principles, using strong authentication for local accounts, and monitoring for unauthorized access attempts. Regularly audit configuration files and system permissions to ensure sensitive files are not world-readable or accessible by unauthorized users. Although no patches are currently listed, organizations should monitor IBM security advisories closely and apply updates or patches as soon as they become available. Employ container security best practices such as isolating containers, using minimal base images, and scanning container images for vulnerabilities. Additionally, consider implementing host-based intrusion detection systems (HIDS) to detect suspicious local activities. Finally, conduct security awareness training to reduce insider threat risks and ensure that local users understand the importance of securing credentials and configuration files.

Description

IBM Security Access Manager Docker 10.0.0.0 through 10.0.7.1 could allow a local user to possibly elevate their privileges due to sensitive configuration information being exposed. IBM X-Force ID: 292413.

Impact

For European organizations, the primary impact of this vulnerability is the potential unauthorized disclosure of sensitive configuration credentials, which can lead to privilege escalation on systems running IBM Security Verify Access Docker. This could allow attackers to bypass access controls, potentially gaining administrative capabilities within the affected environment. Given that IBM Security Verify Access is often deployed in environments managing authentication and authorization, exploitation could undermine the security of multiple dependent applications and services. The vulnerability’s local access requirement limits remote exploitation but increases risk in environments where insider threats or compromised local accounts exist. Organizations in sectors such as finance, government, healthcare, and critical infrastructure in Europe, which rely heavily on IBM security products, could face increased risk of lateral movement and privilege escalation attacks. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits over time.

Summary

CVE-2024-35137 is a vulnerability identified in IBM Security Verify Access Docker versions 10.0.0.0 through 10.0.7.1, categorized under CWE-258 (Use of Empty Password with Configuration File). The issue arises because the product’s configuration file contains an empty password or insufficiently protected sensitive credentials, which can be accessed by a local user. This exposure allows an attacker with local access to the host system to read sensitive configuration data, potentially including credentials or tokens, which can then be leveraged to escalate privileges within the system. The vulnerability does not require prior authentication or user interaction, but it does require local access to the system hosting the Docker container. The CVSS v3.1 base score is 6.2 (medium severity), reflecting a high impact on confidentiality but no impact on integrity or availability. The attack vector is local (AV:L), with low attack complexity (AC:L), no privileges required (PR:N), and no user interaction (UI:N). The scope remains unchanged (S:U). No public exploits have been reported yet, but the exposure of sensitive configuration data in a security-critical product like IBM Security Verify Access Docker poses a significant risk if local access controls are weak or compromised. This product is used in enterprise environments for identity and access management, often protecting critical applications and services.

CWE-258Empty Password in Configuration File (opens in a new tab)
Variant weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
Using an empty string as a password is insecure.
System Configuration
Passwords should be at least eight characters long -- the longer the better. Avoid passwords that are in any way similar to other passwords you have. Avoid using words that may be found in a dictionary, names book, on a map, etc. Consider incorporating numbers and/or punctuation into your password.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V2.1.2 (opens in a new tab)
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:01 UTC

WeaknessesCWE-258

Technical details

References

Community reviews

Related threats