CVE-2023-45249
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 · uneditedRemote command execution due to use of default passwords. The following products are affected: Acronis Cyber Infrastructure (ACI) before build 5.0.1-61, Acronis Cyber Infrastructure (ACI) before build 5.1.1-71, Acronis Cyber Infrastructure (ACI) before build 5.2.1-69, Acronis Cyber Infrastructure (ACI) before build 5.3.1-53, Acronis Cyber Infrastructure (ACI) before build 5.4.4-132.
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 confidenceRemote command execution vulnerability in Acronis Cyber Infrastructure due to use of default passwords. Attackers can exploit default credentials to gain unauthorized access and execute arbitrary commands on affected systems.
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< 5.0.1-61>= 5.1.1, < 5.1.1-71>= 5.2.1, < 5.2.1-69>= 5.3.1, < 5.3.1-53>= 5.4.4, < 5.4.4-132CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify Acronis Cyber Infrastructure installationLocate the Acronis Cyber Infrastructure installation directory or identify the running service using system inventory tools or package managersAffected if The product is installed on the system
-
Determine installed versionRetrieve the installed version of Acronis Cyber Infrastructure using the product's version command, management interface, or installation metadataAffected if The version falls within any of the affected ranges: < 5.0.1-61; >= 5.1.1 and < 5.1.1-71; >= 5.2.1 and < 5.2.1-69; >= 5.3.1 and < 5.3.1-53; >= 5.4.4 and < 5.4.4-132
-
Inspect for default credentialsExamine configuration files, credential storage, or authentication settings for the presence of default passwords used during initial setup or for service accountsAffected if Default passwords are present or have not been changed from manufacturer defaults
-
Verify administrative access without authenticationTest whether the management interface or API accepts connections without credentials using the known default credential pairsAffected if Authentication can be bypassed or default credentials grant administrative access
-
Check network exposureDetermine if the management interface is exposed to untrusted networks by reviewing firewall rules, network configuration, and listening servicesAffected if The system is accessible from untrusted networks on ports used for management
The system is affected if Acronis Cyber Infrastructure is installed with a version matching the affected ranges AND the default credentials have not been changed AND the management interface is network-accessible.
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 · scoped5.0.1-615.1.1-715.2.1-69
Update Acronis Cyber Infrastructure to version 5.0.1-61, 5.1.1-71, 5.2.1-69, 5.3.1-53, or 5.4.4-132 or later. Change all default passwords to strong, unique passwords immediately.
Upgrade to the fixed build for your version line: 5.0.1-61, 5.1.1-71, 5.2.1-69, 5.3.1-53, or 5.4.4-132 (or later)
- Identify the currently installed Acronis Cyber Infrastructure build version
- For version 5.0.x systems: upgrade to build 5.0.1-61 or later
- For version 5.1.x systems: upgrade to build 5.1.1-71 or later
- For version 5.2.x systems: upgrade to build 5.2.1-69 or later
- For version 5.3.x systems: upgrade to build 5.3.1-53 or later
- For version 5.4.x systems: upgrade to build 5.4.4-132 or later
- After upgrade, change any default credentials used during setup to strong, unique passwords
- Verify the upgrade was successful and the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-45249 — 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-45249 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