dbcve.org
AgentApplication · Acronis

CVE-2023-4688

MEDIUM · 5.5 CVSS v3.1 Published 2023-08-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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 leak through log files. The following products are affected: Acronis Agent (Linux, macOS, Windows) before build 35433.

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 confidence

Acronis Agent writes sensitive information to log files before build 35433, allowing local attackers or log viewers to potentially access credentials, tokens, or other confidential data exposed in the agent's log output.

MitigationUpgrade Acronis Agent to build 35433 or later across all affected Linux, macOS, and Windows systems to eliminate the sensitive data leakage in logs.

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
AgentApplication
Affected:< c23.05

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Acronis Agent installation
    Check for running Acronis Agent processes or installed software. On Windows, open Services and look for 'Acronis Agent' or 'Acronis Cyber Protect' service. On Linux/macOS, run 'ps aux | grep acronis' or check for /opt/acronis directory.
    Affected if Acronis Agent is found running or installed on the system.
  2. Identify installed Acronis Agent build version
    Locate the Acronis Agent version information. On Windows, right-click the Acronis icon in system tray and select 'About' or check Add/Remove Programs for the version. On Linux, run '/opt/acronis/bin/acroagent --version' or check '/opt/acronis/bin/' directory contents. On macOS, check Application folder or run the agent binary with --version flag.
    Affected if The build number returned is below 35433 (or version is shown as c23.05 or earlier).
  3. Compare against vulnerable version threshold
    Compare the discovered build number to the fixed version. Vulnerable versions are those with build numbers less than 35433 (pre-c23.05). If you see a version like 'c23.04' or build numbers like 35400-series, these are affected.
    Affected if Installed build is below 35433, indicating the agent writes sensitive data to logs.
  4. Inspect agent log files for exposed credentials
    Locate Acronis Agent log directories. Common paths include: Windows: %ProgramData%\Acronis\ or %ProgramData\Acronis Agent\Logs\; Linux: /var/log/acronis/ or /opt/acronis/var/log/; macOS: /Library/Logs/Acronis/ or /var/log/acronis/. Search these logs for patterns like passwords, tokens, API keys, or credential strings using 'grep -i password' or similar search.
    Affected if Log files contain plaintext credentials, tokens, API keys, or other sensitive data that should not be exposed.

If Acronis Agent is installed with a build number below 35433 (or version c23.05) and log files contain sensitive information, the environment is vulnerable to CVE-2023-4688.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Acronis Agent to build 35433 or later across all affected Linux, macOS, and Windows systems to eliminate the sensitive data leakage in logs.

Recommended fix High confidence

Acronis Agent c23.05 (build 35433)

  1. 1. Identify the current Acronis Agent version installed on the system (Linux, macOS, or Windows).
  2. 2. Download Acronis Agent version c23.05 (build 35433) or later from the official Acronis download center or your licensed Acronis account.
  3. 3. Before upgrading, ensure proper backup of current configuration and data.
  4. 4. Upgrade the Acronis Agent to version c23.05 (build 35433) or newer.
  5. 5. After upgrade, verify that sensitive information is no longer being written to log files.
  6. 6. Review existing log files for any sensitive information that may have been previously logged and redact as necessary.
Caveat Standard upgrade - verify compatibility with your Acronis management infrastructure and test in non-production environment first

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

Fix this in Agent Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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 locally
dbcve dependency scanner

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