CVE-2023-41742
Acronis Cyber Protect 15
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-41742 is a high-severity Binding to an Unrestricted IP Address (CWE-1327) vulnerability in Acronis Cyber Protect. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Steganography (T1001.002); ranked at the 41th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-46234
Vulnerability Data
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Controls whether organization resources are exposed to external system spheres by permitting or prohibiting their use.
The control ensures information is not released into a security sphere where the recipient lacks matching access authorizations.
The control ensures information resources are not exposed to the incorrect (public) sphere through review and authorization.
Protects against data mining that would expose resources to unauthorized spheres by enforcing detection and controls.
Restricts information flows to ensure resources are not exposed to incorrect or unauthorized spheres.
Controlling internal connections prevents exposure of resources to unintended internal spheres.
Knowing exact processing and storage locations helps avoid exposure of resources to incorrect spheres.
The control prevents exposure of the media resource to the wrong security sphere.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Documenting authorized network flows informs correct bind decisions and reduces the chance of 0.0.0.0 usage.
Network protection controls directly prevent exposure via unrestricted binds while fixing the weakness addresses only one vector of unauthorized access.
Configuration management enforces restricted bind addresses, covering the weakness completely but only one aspect of overall hardening.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Network security controls directly require restricting listening interfaces to specific addresses rather than 0.0.0.0.
A.8.21 requires identifying, requiring and monitoring security features (including authentication, authorization and network connection controls) from providers and formulating rules on allowed networks/services; it does not stop a product from binding to 0.0.0.0 and the weakness remains exploitable until the binding itself is changed.
Network segregation can limit the blast radius of an unrestricted binding but does not prevent the binding itself.
Secure architecture principles discourage exposing services on all interfaces, though the control is broader than this single weakness.
Secure coding guidance can catch hard-coded 0.0.0.0 bindings during development but is not the primary mitigation.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.