CVE-2023-45245
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 · uneditedSensitive information disclosure due to missing authorization. The following products are affected: Acronis Agent (Linux, macOS, Windows) before build 36119.
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 confidenceAcronis Agent fails to enforce authorization checks on certain operations, allowing unauthenticated or improperly authenticated users to access sensitive information. The vulnerability exists in Linux, macOS, and Windows versions prior to build 36119.
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.08CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Verify Acronis Agent installationUse system tools to list installed software (Windows: Programs and Features, Linux: dpkg/rpm -qa, macOS: system_profiler or ls /Applications) and confirm Acronis Agent is presentAffected if Acronis Agent is installed on the system
-
Determine installed build numberQuery the Acronis Agent for its version/build information. On Windows check registry key HKLM\SOFTWARE\Acronis\Agent\ or use 'agent_version' command if available. On Linux check /etc/acronis/version or run 'acronis_agent version'. On macOS check /Library/Application Support/Acronis/Agent/version or the application bundle infoAffected if The build number returned is less than 36119 or the version shows c23.08 or earlier (any build prior to 36119)
-
Confirm operating system is affectedIdentify the OS where Acronis Agent is installed. The vulnerability affects Linux, macOS, and Windows versions prior to build 36119Affected if The system is running Linux, macOS, or Windows with Acronis Agent version before build 36119
A system is affected if Acronis Agent is installed and its build number is below 36119 (or version c23.08) on Linux, macOS, or Windows.
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 · scopedUpgrade Acronis Agent to build 36119 or later to obtain the authorization fix.
Acronis Agent c23.08 (build 36119) or later
- Identify the current Acronis Agent version installed on all affected systems (Linux, macOS, and Windows)
- Access the Acronis download portal or management console
- Download Acronis Agent version c23.08 or later (build 36119 or higher)
- Schedule a maintenance window for the upgrade process
- Back up current Agent configuration settings if possible
- Upgrade the Acronis Agent on Linux systems to build 36119 or later
- Upgrade the Acronis Agent on macOS systems to build 36119 or later
- Upgrade the Acronis Agent on Windows systems to build 36119 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-45245 — 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-45245 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