# CVE-2024-25650: Information disclosure in n/a

> A PAM administrator can obtain the symmetric key to impersonate the Engine and exfiltrate sensitive RabbitMQ messages without audit logging.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Mar 2024
- **Updated:** 21 Nov 2024
- **Also known as:** GHSA-25gj-3mw9-4cjw

## What is CVE-2024-25650?

CVE-2024-25650 is a medium-severity vulnerability in n/a, published on 14 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2024-25650?

It affects 2 products.


Products: Delinea Distributed Engine, Delinea Secret Server.

## How do I fix CVE-2024-25650?

No fix has been published for CVE-2024-25650 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-25650 being exploited?

There is no known exploitation of CVE-2024-25650 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-25650 and fix it if it is affected.

What it is: CVE-2024-25650 is a medium-severity vulnerability in n/a, published on 14 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-25650 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-25650/ (Markdown: https://insights.sbomify.com/CVE-2024-25650/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-25650
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-25650
- OSV: https://osv.dev/vulnerability/CVE-2024-25650

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-25650/
Summaries are generated and may contain mistakes; the official description above is the record.