CVE-2024-39206
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMSP360 Backup Agent versions 7.8.5.15 and 7.9.4.84 store network share credentials in an enginesettings.list file that is encrypted but uses a hard-coded encryption key. Any attacker who obtains the encrypted file or the key can decrypt the stored credentials, exposing authentication material for network shares used in backup jobs.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if MSP360 Backup Agent is installedLook for the MSP360 Backup Agent installation directory, typically under C:\Program Files\MSP360\Backup Agent or C:\Program Files (x86)\MSP360\Backup Agent on Windows systems. Also check Programs and Features (Add/Remove Programs) for MSP360 Backup Agent entry.Affected if MSP360 Backup Agent is installed on the system
-
Identify the installed MSP360 Backup Agent versionOpen the application, go to Help > About, or check the installed programs list in Windows Control Panel. Compare the version against 7.8.5.15 and 7.9.4.84.Affected if The installed version is 7.8.5.15 or 7.9.4.84
-
Locate the enginesettings.list fileNavigate to the MSP360 Backup Agent configuration directory, typically found in %APPDATA%\MSP360\Backup Agent\ or the installation folder. Look for a file named enginesettings.list.Affected if The enginesettings.list file exists in the MSP360 configuration directory
-
Verify the file contains encrypted credential dataOpen enginesettings.list with a text editor and look for encrypted or encoded strings that appear to be credential data (usernames, passwords, or network share paths). The file should contain base64-encoded or otherwise encrypted credential material.Affected if The enginesettings.list file contains encrypted credential strings related to network shares or backup job authentication
A user is affected if MSP360 Backup Agent version 7.8.5.15 or 7.9.4.84 is installed AND the enginesettings.list file exists with encrypted network share credentials.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataThe vendor must replace the hard-coded encryption key with proper key management (e.g., derived from user credentials, key derivation functions, or secure key storage) and re-encrypt existing stored credentials using the new mechanism.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-39206 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-39206 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data