{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-29855 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-29855 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-29855 is a critical vulnerability in Veeam Recovery Orchestrator, published on 11 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-29855 and fix it if it is affected.\n\nWhat it is: CVE-2024-29855 is a critical vulnerability in Veeam Recovery Orchestrator, published on 11 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-29855 in the wild and no public exploit code.\n\nAffected product: Veeam Recovery Orchestrator. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-29855/ (Markdown: https://insights.sbomify.com/CVE-2024-29855/index.md)","id":"CVE-2024-29855","markdown":"https://insights.sbomify.com/CVE-2024-29855/index.md","name":"CVE-2024-29855","record":{"aliases":["GHSA-vfmf-3vr6-j85g"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Veeam Recovery Orchestrator","requires_auth":"none","summary":"Attackers can bypass authentication in Veeam Recovery Orchestrator using a hard-coded JWT secret, potentially taking over accounts.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"recovery_orchestrator","vendor":"veeam"}],"cvss":{"score":9,"severity":"critical","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"Hard-coded JWT secret allows authentication bypass in Veeam Recovery Orchestrator","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2024-06-13","github_poc":1,"max_poc_stars":19,"metasploit":0,"nuclei":0,"refs":[{"date":"2024-06-13T08:32:55Z","kind":"github_poc","ref":"https://github.com/sinsinology/CVE-2024-29855","stars":19,"title":"PoC for the Veeam Recovery Orchestrator Authentication CVE-2024-29855"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Hardcoded credentials in Recovery Orchestrator","id":"CVE-2024-29855","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Bouncy Castle certificate parsing issues cause high CPU usage during parameter evaluation.","id":"CVE-2024-29857"},"packages":[],"prev":{"headline":"Auth bypass in Agent for Windows","id":"CVE-2024-29853"},"products":["Recovery Orchestrator"],"published":"2024-06-11","related":[{"cvss_score":8.8,"headline":"Information disclosure in Availability Orchestrator","id":"CVE-2024-22022","kev_date_added":null,"published":"2024-02-07"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-03-27","vendors":["Veeam"]},"summary":"Attackers can bypass authentication in Veeam Recovery Orchestrator using a hard-coded JWT secret, potentially taking over accounts.","url":"https://insights.sbomify.com/CVE-2024-29855/"}