dbcve.org
Veeam Agent For WindowsApplication · Veeam

CVE-2024-29853

HIGH · 7.8 CVSS v3.0 Published 2024-05-22
Fix available
A fix is available. Upgrade to 6.1.2.134 or later.
See remediation →
80/100
Remediation priority · High
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
An authentication bypass vulnerability in Veeam Agent for Microsoft Windows allows for local privilege escalation.

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

The vulnerability allows a local authenticated attacker to bypass authentication mechanisms in Veeam Agent for Microsoft Windows and escalate privileges to SYSTEM level, potentially giving them full control over the affected Windows machine.

MitigationApply the vendor-provided security update for Veeam Agent for Windows. Verify that the backup/restore functionality continues to operate correctly after patching.

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
Veeam Agent For WindowsApplication
Affected:< 6.1.2.134

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
High
Availability
High

CVSS:3.0/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 checks

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

  1. Verify Veeam Agent for Windows is installed
    Open Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*Veeam*"}' in PowerShell to list installed Veeam components
    Affected if Veeam Agent for Windows appears in the installed programs list
  2. Determine the installed version number
    In Programs and Features, click on Veeam Agent for Windows and view the Version column, or query the registry key 'HKLM\SOFTWARE\Veeam\Veeam Agent for Windows' (or 'HKLM\SOFTWARE\WOW6432Node\Veeam\Veeam Agent for Windows') for a 'Version' or 'ProductVersion' value
    Affected if The displayed version is lower than 6.1.2.134 or the version cannot be determined but the product is present
  3. Confirm the service is running
    Open Services (services.msc) and locate 'Veeam Agent for Windows' service, or run 'Get-Service Veeam*' in PowerShell
    Affected if The Veeam Agent service exists and is running (indicates the vulnerable component is active)
  4. Check for evidence of local user access
    Review Windows Event Viewer Security logs for Event ID 4624 (successful logon) with Veeam-related process names, or check 'whoami /all' output to see current user privileges
    Affected if A non-privileged authenticated user account has local access to the machine (required condition for the privilege escalation exploit)

If Veeam Agent for Windows is installed with a version lower than 6.1.2.134 and a local authenticated user exists on the system, the environment is potentially affected by this privilege escalation vulnerability.

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 6.1.2.134 or later
Fixed in 6.1.2.134
Interim mitigation

Apply the vendor-provided security update for Veeam Agent for Windows. Verify that the backup/restore functionality continues to operate correctly after patching.

Recommended fix High confidence

Veeam Agent for Windows 6.1.2.134 or later

  1. Navigate to the Veeam downloads page or your Veeam Customer Portal
  2. Download Veeam Agent for Windows version 6.1.2.134 or later
  3. Ensure all backup jobs are paused or completed before proceeding
  4. Run the installer with administrative privileges
  5. Follow the upgrade wizard prompts to complete the installation
  6. Restart the computer if prompted by the installer
  7. Verify the installed version matches the fixed release (6.1.2.134 or later)
Caveat Standard upgrade; ensure backup jobs are paused and test in non-production environment first

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

Fix this in Veeam Agent For Windows Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
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,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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