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

> Attackers can obtain network share credentials from backup settings due to a hard-coded encryption key, exposing sensitive data.

- **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:** 2 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-6q3c-chw7-6f3j

## What is CVE-2024-39206?

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

### Official description

An issue discovered in MSP360 Backup Agent v7.8.5.15 and v7.9.4.84 allows attackers to obtain network share credentials used in a backup due to enginesettings.list being encrypted with a hard coded key.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2024-39206 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-39206 is a high-severity vulnerability in n/a, published on 2 Jul 2024. 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-39206 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-39206/ (Markdown: https://insights.sbomify.com/CVE-2024-39206/index.md)
```

## Sources

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

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