dbcve.org
OneApplication · Veeam

CVE-2024-42024

HIGH · 8.8 CVSS v3.1 Published 2024-09-07
Fix available
A fix is available. Upgrade to 12.2.0.4093 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
A vulnerability that allows an attacker in possession of the Veeam ONE Agent service account credentials to perform remote code execution on the machine where the Veeam ONE Agent is installed.

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

This is an authentication-required remote code execution vulnerability in Veeam ONE Agent. An attacker who obtains the Veeam ONE Agent service account credentials can execute arbitrary code on the host where the Veeam ONE Agent is installed, effectively gaining full system compromise under the context of the service account.

MitigationLimit exposure by protecting service account credentials through strong password policies, credential hygiene, and network segmentation; apply vendor patches when available; implement least privilege for the service account to reduce blast radius.

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
OneApplication
Affected:>= 12.0.0.2498, < 12.2.0.4093

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 ONE installation
    Check if Veeam ONE is installed by looking for the application in Windows Programs and Features, or search for Veeam ONE components in the installation directory (typically C:\Program Files\Veeam\One or C:\Program Files (x86)\Veeam\One).
    Affected if Veeam ONE is found on the system
  2. Determine installed Veeam ONE version
    Open Windows Programs and Features, locate Veeam ONE in the list, and note the version column. Alternatively, open Registry Editor and navigate to HKLM\SOFTWARE\Veeam\Veeam ONE\Components\ or check the version info of the Veeam ONE service executable.
    Affected if A version is displayed in the Programs list or found in registry
  3. Compare version against affected range
    Compare the installed version number to the affected range: versions 12.0.0.2498 through 12.2.0.4092 are vulnerable. Versions below 12.0.0.2498 or at/above 12.2.0.4093 are not affected.
    Affected if Installed version is greater than or equal to 12.0.0.2498 AND less than 12.2.0.4093
  4. Identify Veeam ONE service account
    Open Services console (services.msc), find the Veeam ONE service, right-click and select Properties, then note the account name listed under 'Log On As'. This is the service account that could be exploited if the vulnerability is present.
    Affected if A service account is configured for Veeam ONE (this confirms the attack surface exists, though version check is the primary determinant)

The environment is affected if Veeam ONE is installed with a version >= 12.0.0.2498 and < 12.2.0.4093, regardless of the service account 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 12.2.0.4093 or later
Fixed in 12.2.0.4093
Interim mitigation

Limit exposure by protecting service account credentials through strong password policies, credential hygiene, and network segmentation; apply vendor patches when available; implement least privilege for the service account to reduce blast radius.

Recommended fix High confidence

Veeam ONE 12.2.0.4093 or later

  1. 1. Verify current Veeam ONE Agent version by checking the installed software or checking the version through Veeam ONE Client
  2. 2. Download Veeam ONE version 12.2.0.4093 or later from the official Veeam download portal at www.veeam.com
  3. 3. Plan maintenance window as upgrade will require service restart
  4. 4. Backup Veeam ONE configuration data before proceeding
  5. 5. Run the installer with appropriate administrative privileges
  6. 6. Follow the upgrade wizard prompts, selecting upgrade option
  7. 7. Verify the upgrade completed successfully by checking the new version number
  8. 8. Confirm Veeam ONE services are running properly
Caveat Standard upgrade - review Veeam release notes for any configuration or feature changes between versions

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

Fix this in One Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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