CVE-2024-49387
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 · uneditedCleartext transmission of sensitive information in acep-collector service. The following products are affected: Acronis Cyber Protect 16 (Linux, Windows) before build 38690.
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 · moderate confidenceThe acep-collector service in Acronis Cyber Protect 16 transmits sensitive data in cleartext (unencrypted) rather than using TLS/SSL encryption. This allows network eavesdroppers to intercept and read sensitive information passing between clients and the collector service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 15= 16CVSS 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.
-
Identify if acep-collector service is runningOn the Acronis server, check running services or processes for acep-collector. On Windows, use Services console or 'sc query acep-collector'. On Linux, use 'systemctl status acep-collector' or 'ps aux | grep acep-collector'.Affected if The acep-collector service is installed and running on the system.
-
Determine installed Acronis Cyber Protect versionCheck the installed version of Acronis Cyber Protect. On Windows, look in Programs and Features or registry. On Linux, check the RPM/DEB package version or run the Acronis management tool if available. Compare your version against the affected ranges: version 16 or any version <= 15.Affected if The installed version is 16 or lower (15, 14, etc.).
-
Inspect acep-collector service configuration for SSL/TLS settingsLocate the acep-collector configuration file. Check for parameters related to SSL, TLS, encryption, or secure communication. Look for settings such as 'use_ssl', 'enable_tls', 'ssl_enabled', or similar flags. Also check for HTTP (unencrypted) vs HTTPS (encrypted) endpoint configurations.Affected if TLS/SSL encryption is explicitly disabled or not configured for the acep-collector service.
-
Verify network communication method used by acep-collectorUse network monitoring tools (netstat, ss, or Wireshark) to capture traffic from the acep-collector service. Observe whether the service communicates on unencrypted ports (HTTP typically port 80) or encrypted ports (HTTPS typically port 443). Check the collector's configuration for listening ports and protocol settings.Affected if The acep-collector service listens on or communicates via unencrypted HTTP ports instead of HTTPS/SSL ports.
You are affected if the acep-collector service is running on Acronis Cyber Protect version 16 or lower and TLS/SSL encryption is disabled in its configuration, resulting in cleartext transmission of sensitive data.
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 dataEnable TLS encryption for the acep-collector service and ensure all communications use HTTPS or encrypted protocols. Update to build 38690 or later which should contain the fix.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49387 — 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-49387 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