# CVE-2024-52884: Weak cryptography in n/a

> Attackers with access to configuration exports can decrypt passwords due to weak obfuscation in AudioCodes Mediant SBC.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/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:** 7 Feb 2025
- **Updated:** 10 Feb 2025
- **Also known as:** GHSA-v6vm-3qpv-vj6x

## What is CVE-2024-52884?

CVE-2024-52884 is a high-severity vulnerability in n/a, published on 7 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in AudioCodes Mediant Session Border Controller (SBC) before 7.40A.501.841. Due to the use of weak password obfuscation/encryption, an attacker with access to configuration exports (INI) is able to decrypt the passwords.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

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

It affects 1 product.


Products: Audiocodes Mediant Session Border Controller.

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

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

## Is CVE-2024-52884 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-52884 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-52884 is a high-severity vulnerability in n/a, published on 7 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-52884 exists.

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-52884/ (Markdown: https://insights.sbomify.com/CVE-2024-52884/index.md)
```

## Sources

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

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