# CVE-2024-52881: Hardcoded credentials in n/a

> Attackers can decrypt sensitive data like passwords from topology files due to a hard-coded key in AudioCodes OVOC.

- **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-9m28-7q5q-gch7

## What is CVE-2024-52881?

CVE-2024-52881 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 One Voice Operations Center (OVOC) before 8.4.582. Due to the use of a hard-coded key, an attacker is able to decrypt sensitive data such as passwords extracted from the topology file.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

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

It affects 1 product.


Products: Audiocodes One Voice Operations Center.

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

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

## Is CVE-2024-52881 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-52883](https://insights.sbomify.com/CVE-2024-52883/): Path traversal in n/a (high 7.5)
- [CVE-2024-52882](https://insights.sbomify.com/CVE-2024-52882/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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