dbcve.org
AgentApplication · Acronis

CVE-2023-41742

HIGH · 7.5 CVSS v3.1 Published 2023-08-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Excessive attack surface due to binding to an unrestricted IP address. The following products are affected: Acronis Agent (Linux, macOS, Windows) before build 30430, Acronis Cyber Protect 15 (Linux, macOS, Windows) before build 35979.

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 confidence

The Acronis Agent and Cyber Protect 15 products bind to all network interfaces (0.0.0.0) instead of restricting to localhost or specific IP addresses, exposing the service to remote network attackers and creating excessive attack surface.

MitigationUpdate to Acronis Agent build 30430 or Cyber Protect 15 build 35979 or later. Alternatively, use network firewall rules to restrict access to the affected service ports.

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
AgentApplication
Affected:< c22.09
Cyber ProtectApplication
Affected:= 15

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Acronis product installation and version
    Check installed version of Acronis Agent or Cyber Protect 15. On Windows, inspect 'Add/Remove Programs' or check the product's About/Version information in the management console. On Linux, use 'rpm -qa | grep acronis' or 'dpkg -l | grep acronis'.
    Affected if Acronis Agent version is earlier than c22.09, or Cyber Protect 15 is installed (any build)
  2. Identify Acronis service listening ports
    Run 'netstat -anp | grep -i acronis' (Linux) or 'netstat -ano | findstr acronis' (Windows) to find which ports the Acronis services are listening on.
    Affected if Acronis services are found listening on any port
  3. Determine network binding address
    For each identified Acronis service port, check the local address it binds to. Use 'ss -tlnp | grep <port>' or examine the service configuration files to see if it binds to 0.0.0.0 or a specific interface.
    Affected if The service binds to 0.0.0.0 (all interfaces) instead of 127.0.0.1 (localhost) or a specific internal IP
  4. Verify external accessibility
    From a machine on a different subnet, attempt to connect to the Acronis service ports (common ports: 9876, 7780, 8443, or check your netstat results). Also review host-based firewall rules with 'netsh advfirewall firewall show rule name=all' (Windows) or 'iptables -L' (Linux).
    Affected if The Acronis service ports are reachable from remote hosts or firewall allows external access

You are affected if Acronis Agent version is earlier than c22.09 or Cyber Protect 15 is installed AND the service binds to 0.0.0.0 making it accessible from remote network locations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to Acronis Agent build 30430 or Cyber Protect 15 build 35979 or later. Alternatively, use network firewall rules to restrict access to the affected service ports.

Recommended fix High confidence

Acronis Agent c22.09 (build 30430) or later; Acronis Cyber Protect 15 build 35979 or later

  1. 1. Identify the currently installed Acronis Agent version by running: /opt/acronis/bin/m广告 --version (Linux) or checking in Control Panel (Windows)
  2. 2. Identify the currently installed Acronis Cyber Protect 15 version from the management console or agent status
  3. 3. For Acronis Agent: Upgrade to version c22.09 or later (build 30430 or higher)
  4. 4. For Acronis Cyber Protect 15: Upgrade to build 35979 or later
  5. 5. Download the updated installer from the official Acronis download portal or your licensed subscription channel
  6. 6. Run the installer with appropriate privileges (root/administrator)
  7. 7. Verify the upgrade was successful by checking the new build number matches or exceeds the fixed versions
  8. 8. Restart the Acronis services if required by the upgrade process
Caveat Review release notes for any configuration or migration changes between versions before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Agent Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-41742 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-41742 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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