dbcve.org
OneApplication · Veeam

CVE-2024-42021

MEDIUM · 6.5 CVSS v3.1 Published 2024-09-07
Fix available
A fix is available. Upgrade to 12.2.0.4093 or later.
See remediation →
71/100
Remediation priority · Elevated
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
An improper access control vulnerability allows an attacker with valid access tokens to access saved credentials.

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 improper access control (IDOR-style) vulnerability where the system fails to properly validate if a user should access specific saved credentials, even when presenting a valid access token. An authenticated attacker can access credentials belonging to other users or resources they should not have permission to view.

MitigationImplement proper authorization checks at every point where saved credentials are accessed, ensuring the requesting user owns or has explicit permission to access those specific credentials before returning any credential data.

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

CVSS:3.1/AV:N/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. Identify installed Veeam One version
    Open Veeam One Web UI or navigate to Help > About in the Veeam One Client to view the exact version number (for example: 12.1.0.1234). Alternatively, check the installed software list on the Veeam One server machine.
    Affected if The installed version is 12.0.0.2498 or higher but lower than 12.2.0.4093 (for example: 12.1.0.2000 falls within the affected range).
  2. Confirm Veeam One service is running
    On the Veeam One server, open Services.msc and verify the Veeam One Reporter Service or Veeam One Monitor Service is in Running state, or check via PowerShell: Get-Service Veeam*
    Affected if The Veeam One service is running and accessible, providing the attack surface for an authenticated user to exploit the credential access flaw.
  3. Verify saved credentials feature is in use
    Log into Veeam One Web UI as any authenticated user and navigate to the Credentials or Credential Manager section (typically under Infrastructure > Credentials or Settings > Credentials Management).
    Affected if Multiple saved credentials exist in the system and users can view or reference credentials they did not create, indicating the vulnerable code path may be reachable.

A Veeam One installation is affected if its installed version falls within 12.0.0.2498 through 12.2.0.4092 (inclusive) and the credential management interface is accessible to authenticated users.

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

Implement proper authorization checks at every point where saved credentials are accessed, ensuring the requesting user owns or has explicit permission to access those specific credentials before returning any credential data.

Recommended fix High confidence

12.2.0.4093 or later (12.2.x branch)

  1. 1. Back up the current Veeam ONE configuration and database before proceeding with any upgrade.
  2. 2. Download Veeam ONE version 12.2.0.4093 or later from the official Veeam download portal at www.veeam.com.
  3. 3. Stop all Veeam ONE services to ensure a stable upgrade process.
  4. 4. Run the installer for version 12.2.0.4093 or later and follow the on-screen upgrade wizard prompts.
  5. 5. After upgrade completes, restart all Veeam ONE services.
  6. 6. Verify the upgrade was successful by checking the Veeam ONE console version information.
  7. 7. Confirm the vulnerability is resolved by verifying that the improper access control issue no longer allows unauthorized credential access.
Caveat Review Veeam ONE 12.2 release notes for any configuration or feature changes before upgrading; test in non-production environment first

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

Fix this in One 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 the upgrade done

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-2024-42021 — 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-42021 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