dbcve.org
Cyber InfrastructureApplication · Acronis

CVE-2023-2360

HIGH · 7.5 CVSS v3.1 Published 2023-04-28
Fix available
A fix is available. Upgrade to 5.2.0-135 or later.
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
Sensitive information disclosure due to CORS misconfiguration. The following products are affected: Acronis Cyber Infrastructure (ACI) before build 5.2.0-135.

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

Cross-Origin Resource Sharing (CORS) misconfiguration in Acronis Cyber Infrastructure allows unauthorized cross-origin requests to access sensitive resources. The CORS policy is set too permissively, potentially allowing malicious websites to make authenticated requests on behalf of users and exfiltrate sensitive data.

MitigationRestrict CORS policy to explicitly allow only trusted origins, and avoid using wildcard (*) origins or overly broad Access-Control-Allow-Origin headers. Upgrade to ACI build 5.2.0-135 or later.

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
Cyber InfrastructureApplication
Affected:< 5.2.0-135

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. Identify if Acronis Cyber Infrastructure is installed
    Check for the ACI service or installation directory - look for /opt/acronis/cyber-infrastructure or run 'systemctl list-units | grep -i acronis' to find running ACI services
    Affected if The product is present on the system
  2. Verify the installed ACI version
    Run the ACI version command or check /opt/acronis/cyber-infrastructure/version file if it exists - compare the build number to 5.2.0-135
    Affected if The installed version is less than 5.2.0-135 (build 135)
  3. Locate the CORS configuration
    Search for CORS-related configuration files - check nginx/apache config directories under /etc/nginx/, /etc/httpd/, or the ACI web server config directory for files containing 'access-control-allow-origin' or 'cors' directives
    Affected if CORS configuration files exist in the web server setup
  4. Inspect Access-Control-Allow-Origin headers
    Examine the CORS configuration files for the Access-Control-Allow-Origin directive - look for wildcard (*) value, missing origin validation, or overly broad origin patterns
    Affected if The Access-Control-Allow-Origin is set to wildcard (*) or allows unrestricted origins
  5. Check CORS allowed origins list
    Review the CORS configuration to determine if origins are explicitly whitelisted or if the policy permits any origin to make cross-origin requests
    Affected if Origins are not explicitly restricted to trusted domains or the policy is overly permissive

The environment is affected if Acronis Cyber Infrastructure is installed with a version earlier than 5.2.0-135 AND the CORS policy permits wildcard or unspecified origins in the Access-Control-Allow-Origin configuration.

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
Upgrade available Upgrade to 5.2.0-135 or later
Fixed in 5.2.0-135
Interim mitigation

Restrict CORS policy to explicitly allow only trusted origins, and avoid using wildcard (*) origins or overly broad Access-Control-Allow-Origin headers. Upgrade to ACI build 5.2.0-135 or later.

Recommended fix Moderate confidence

Acronis Cyber Infrastructure build 5.2.0-135 or later

  1. 1. Back up the current Acronis Cyber Infrastructure configuration and data
  2. 2. Obtain the updated Acronis Cyber Infrastructure build 5.2.0-135 or later from official Acronis distribution channels
  3. 3. Follow Acronis standard upgrade documentation for your deployment type (standalone or cluster)
  4. 4. After upgrade, verify the CORS configuration is properly restricted to trusted domains only
  5. 5. Test that the application functions normally with the corrected CORS policy
Caveat Review Acronis upgrade documentation for any migration requirements between your current version and 5.2.0

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

Fix this in Cyber Infrastructure Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-2360 — 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-2360 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