BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2024-29855High confidence

Hard-coded JWT secret allows authentication bypass in Veeam Recovery Orchestrator

Veeam · Recovery Orchestrator

Official source article: Veeam KB4585 ↗. Check the applicable product and release in the original source.

9.0CriticalCVSS 3.0
Recommended action
Within 72 hours

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 21.63% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Veeam Recovery Orchestrator and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2024-26847

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 72 hours

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.

Patch available
01

What, why and how

Hard-coded JWT secret allows authentication bypass in Veeam Recovery Orchestrator

What

Hard-coded JWT secret allows authentication bypass in Veeam Recovery Orchestrator

Why

A credential embedded in the product can be recovered or reused across installations instead of being unique to one deployment.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may bypass an access boundary or take over an account.

What

Hard-coded JWT secret allows authentication bypass in Veeam Recovery Orchestrator

Why

A credential embedded in the product can be recovered or reused across installations instead of being unique to one deployment.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may bypass an access boundary or take over an account.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Use of Hard-coded Credentials → bypass an access boundary or take over an account
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-798 ↗

CWE-798: Use of Hard-coded Credentials. The product contains hard-coded credentials, such as a password or cryptographic key.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Common Vulnerability Scoring System 3.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
Stolen credentials, tokens and legitimate administration functions may provide continued access without deploying a large custom toolset.
NetworkUnauthenticatedCWE-798
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

Cyber Security Agency of Singapore · English · CSA-SB-20240612Security Bulletin 12 Jun 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 12 Jun 2024, published on 12 June 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0474Vulnérabilité dans Veeam Recovery Orchestrator

Une vulnérabilité a été découverte dans Veeam Recovery Orchestrator. Elle permet à un attaquant de provoquer un contournement de la politique de sécurité.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-026338Veeam の recovery orchestrator におけるハードコードされた認証情報の使用に関する脆弱性

Veeam の recovery orchestrator には、ハードコードされた認証情報の使用に関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Recovery Orchestrator: 7.1.0.230 < 7.1.0.230, 7.0.0.379 < 7.0.0.379
Fixed
Action
Apply the fixed release for the affected product branch as recorded by Veeam. Validate the exact product and build in the linked advisory before deployment.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 11 Jun 2024 · Last source change 27 Mar 2025, 21:09 UTC · CWE-798 · Use of Hard-coded Credentials

CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2024-26847
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCISA ADP
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    7.1.0.230 < 7.1.0.230; 7.0.0.379 < 7.0.0.379 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    7.1.0.230 < 7.1.0.230; 7.0.0.379 < 7.0.0.379 · Fixed: All customers are advised to upgrade their Veeam Recovery Orchestrator deployment to version 7.1.0.278 or higher.; Download VRO 7.0.0.337 to 7.0.0.379 Patch; Download VRO 7.1.0.205 to 7.1.0.230 Patch; For Veeam Recovery Orchestrator build 7. 0.0.337; For Veeam Recovery Orchestrator build 7. 1.0.205; For environments operating VRO 7.0.0.337, either upgrade to 7.1.0.230 or install the following patch to update to build 7.0.0.379.; For environments operating VRO 7.1.0.205, install the following patch to update to build 7.1.0.230.; The patches below only resolve the vulnerability documented in this article for Veeam Recovery Orchestrator. They do not mitigate the announced vulnerabilities that exist in the build of Veeam Backup & Replication used by Veeam Recovery Orchestrator 7.0.0.337 or 7.1.0.205. For that reason, we strongly encourage all customers to upgrade to Veeam Recovery Orchestrator version 7.1.0.278 or higher, which utilizes the latest Veeam Backup & Replication and Veeam ONE releases to mitigate the vulnerabilities announced in KB4649.
    Veeam ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Veeam ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2024-26847↗CVE authority or vendor reference · Veeam KB4585↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2024-29855 · cve.blacktree.nl