CVE-2023-41743
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 · uneditedLocal privilege escalation due to insecure driver communication port permissions. The following products are affected: Acronis Cyber Protect Home Office (Windows) before build 40278, Acronis Cyber Protect Cloud Agent (Windows) before build 31637, Acronis Cyber Protect 15 (Windows) before build 35979, Acronis True Image OEM (Windows) before build 42575.
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 confidenceLocal privilege escalation vulnerability in Acronis Windows products due to insecure driver communication port permissions. The driver (likely using a named pipe or similar IPC mechanism for user-mode to kernel-mode communication) lacks proper access control, allowing a low-privilege local user to manipulate the driver communication port and escalate to SYSTEM privileges.
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< c23.02= 15all versions= 39900= 40107= 40173= 40208CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 Acronis agent is installedOpen Control Panel > Programs and Features, or run: Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like '*Acronis*'}Affected if Any Acronis product (Agent, Cyber Protect, Cyber Protect Home Office, True Image) appears in the installed programs list
-
Identify Acronis serviceOpen Services (services.msc) or run: Get-Service | Where-Object {$_.DisplayName -like '*Acronis*'}Affected if An Acronis-related service is running on the system
-
Determine Acronis build versionCheck the installed version from Add/Remove Programs, or look in the Acronis program directory for a version/build file, or run: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Acronis*'} | Select-Object DisplayName, DisplayVersionAffected if For Acronis Agent: version is earlier than c23.02; For Cyber Protect 15: version equals 15; For Cyber Protect Home Office: version equals 39900, 40107, 40173, or 40208; or any version if 'all versions' is indicated
-
Check for Acronis driver presenceOpen Device Manager (devmgmt.msc) and look for Acronis drivers under 'System devices' or 'Software devices', or run: Get-WmiObject Win32_PnPSignedDriver | Where-Object {$_.DeviceID -like '*Acronis*' -or $_.DriverDescription -like '*Acronis*'}Affected if An Acronis driver is present in Device Manager
-
Inspect driver communication port permissionsUse Process Explorer or Process Hacker to examine the security descriptor of the Acronis driver communication port (typically a named pipe), or run: Get-Process -Name acronis* | Select-Object Id, Name, PathAffected if The Acronis driver process is accessible by a low-privilege user and the IPC port allows manipulation by non-privileged accounts
You are affected if an Acronis product is installed with a version matching the vulnerable ranges AND the Acronis driver/service is running on the system with exploitable IPC port permissions accessible to low-privilege users.
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.
dbcve · scopedUpdate affected Acronis products to the specified build versions or later: Cyber Protect Home Office to build 40278+, Cyber Protect Cloud Agent to build 31637+, Cyber Protect 15 to build 35979+, and True Image OEM to build 42575+.
Acronis Cyber Protect Home Office >= build 40278; Cyber Protect Cloud Agent >= build 31637; Cyber Protect 15 >= build 35979; True Image OEM >= build 42575
- Identify which Acronis product is installed: Cyber Protect Home Office, Cyber Protect Cloud Agent, Cyber Protect 15, or True Image OEM
- Check the current build version of the installed product in the application UI or system information
- For Cyber Protect Home Office (Windows): upgrade to build 40278 or later
- For Cyber Protect Cloud Agent (Windows): upgrade to build 31637 or later
- For Cyber Protect 15 (Windows): upgrade to build 35979 or later
- For True Image OEM (Windows): upgrade to build 42575 or later
- Verify the upgrade was successful by checking the new build version
- Restart the system if prompted to complete the installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41743 — 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-2023-41743 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