Skip to main content
VulnerabilityPublished Updated

CVE-2024-25650: Cleartext Transmission

Source CVE Database V5

0

Not known to be exploited · CVSS 5.9 Medium.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
5.9Medium
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:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Mar 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

AI-suggested

To mitigate CVE-2024-25650, organizations should take the following specific actions: 1) Immediately review and restrict PAM administrator privileges to the minimum necessary, ensuring that only fully trusted personnel have such access. 2) Monitor and audit REST API endpoint usage, particularly /pre-authenticate, /authenticate, and /execute-and-respond, for anomalous or unexpected requests that could indicate exploitation attempts. 3) Implement network segmentation and strict access controls to limit exposure of the PAM Secret Server and Distributed Engine components, reducing the attack surface. 4) Employ additional encryption or secure transport mechanisms (e.g., TLS with mutual authentication) for communication between PAM components to prevent key interception. 5) Regularly update and patch PAM software once vendor fixes become available; meanwhile, engage with Delinea support for any recommended interim mitigations or workarounds. 6) Conduct thorough security assessments and penetration testing focused on PAM infrastructure to identify and remediate related weaknesses. 7) Enhance logging and alerting capabilities to detect impersonation or unauthorized message access attempts, compensating for the lack of native audit coverage in this attack scenario.

Description

Insecure key exchange between Delinea PAM Secret Server 11.4 and the Distributed Engine 8.4.3 allows a PAM administrator to obtain the Symmetric Key (used to encrypt RabbitMQ messages) via crafted payloads to the /pre-authenticate, /authenticate, and /execute-and-respond REST API endpoints. This makes it possible for a PAM administrator to impersonate the Engine and exfiltrate sensitive information from the messages published in the RabbitMQ exchanges, without being audited in the application.

References

Community reviews

Loading reviews…