CVE-2024-25655VulnerabilityPublished 18 Mar 2024Updated 28 Aug 2024

CVE-2024-25655: n/a

Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.5Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
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: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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 18 Mar 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

AI-suggested

To mitigate CVE-2024-25655, organizations should implement the following specific measures: 1) Restrict and tightly control read access to the AVSystem UMP application database, ensuring only trusted administrators have such privileges. 2) Audit and monitor database access logs for unusual or unauthorized read operations to detect potential exploitation attempts early. 3) If possible, upgrade to a patched version of AVSystem UMP once available or apply vendor-recommended fixes that address secure storage of LDAP credentials. 4) Implement encryption-at-rest and secure credential storage mechanisms within the application or database to prevent plaintext password exposure. 5) Enforce strong LDAP credential policies, including frequent password rotation and multi-factor authentication, to reduce the impact of credential compromise. 6) Segment the network and isolate management platforms to limit exposure if credentials are leaked. 7) Conduct regular security assessments and penetration testing focused on database access controls and credential management. These steps go beyond generic advice by focusing on access control, monitoring, and secure storage practices tailored to the specific vulnerability context.

Description

Insecure storage of LDAP passwords in the authentication functionality of AVSystem Unified Management Platform (UMP) 23.07.0.16567~LTS allows members (with read access to the application database) to decrypt the LDAP passwords of users who successfully authenticate to web management via LDAP.

Impact

The primary impact of CVE-2024-25655 is the compromise of confidentiality of LDAP credentials stored within the AVSystem UMP database. If an attacker or unauthorized insider obtains read access to the application database, they can decrypt LDAP passwords, potentially allowing them to impersonate legitimate users or escalate privileges within the network. This can lead to unauthorized access to sensitive management interfaces and systems, increasing the risk of further exploitation, data breaches, or disruption of managed devices. Organizations relying on AVSystem UMP for device management and authentication may face increased risk of insider threats or external attackers leveraging stolen credentials for lateral movement. The vulnerability does not directly affect system integrity or availability but can indirectly facilitate attacks that do. Since LDAP is commonly used for centralized authentication in enterprise environments, exposure of these credentials can have broad security implications, especially in environments with high-value targets or critical infrastructure. The absence of known exploits reduces immediate risk, but the vulnerability remains a significant concern for organizations with inadequate database access controls.

CWE-922Insecure Storage of Sensitive Information (opens in a new tab)
Class weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product stores sensitive information without properly limiting read or write access by unauthorized actors.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.6 (opens in a new tab)
V8.2.3 (opens in a new tab)
V8.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

cvcn.gov.it/cvcn/cve/CVE-2024-25655 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 26 Feb 2026, 10:42 UTC

WeaknessesCWE-922

Technical details

References

Community reviews

Related threats