{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-42457 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-42457 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-42457 is a high-severity vulnerability in Veeam Backup \u0026 Replication, published on 4 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-42457 and fix it if it is affected.\n\nWhat it is: CVE-2024-42457 is a high-severity vulnerability in Veeam Backup \u0026 Replication, published on 4 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-42457 in the wild and no public exploit code.\n\nAffected product: Veeam Backup \u0026 Replication. 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-42457/ (Markdown: https://insights.sbomify.com/CVE-2024-42457/index.md)","id":"CVE-2024-42457","markdown":"https://insights.sbomify.com/CVE-2024-42457/index.md","name":"CVE-2024-42457","record":{"aliases":["GHSA-pwc4-hfx3-7qw8"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Backup \u0026 Replication","requires_auth":"low_privilege","summary":"Operators can expose saved plaintext credentials by adding a malicious host, leading to credential theft and potential account takeover.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"veeam_backup_\\\u0026_replication","vendor":"veeam"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"}],"description":"A vulnerability in Veeam Backup \u0026 Replication allows users with certain operator roles to expose saved credentials by leveraging a combination of methods in a remote management interface. This can be achieved using a session object that allows for credential enumeration and exploitation, leading to the leak of plaintext credentials to a malicious host. The attack is facilitated by improper usage of a method that allows operators to add a new host with an attacker-controlled IP, enabling them to retrieve sensitive credentials in plaintext.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Information disclosure in Backup \u0026 Replication","id":"CVE-2024-42457","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2024-42458"},"packages":[],"prev":{"headline":"Missing authorization in Backup \u0026 Replication","id":"CVE-2024-42456"},"products":["Backup \u0026 Replication"],"published":"2024-12-04","related":[{"cvss_score":9.8,"headline":"Veeam Backup and Replication Deserialization","id":"CVE-2024-40711","kev_date_added":"2024-10-17","published":"2024-09-07"},{"cvss_score":9.8,"headline":"Veeam Backup \u0026 Replication Remote Code Execution","id":"CVE-2022-26501","kev_date_added":"2022-12-13","published":"2022-03-17"},{"cvss_score":8.8,"headline":"Veeam Backup \u0026 Replication Remote Code Execution","id":"CVE-2022-26500","kev_date_added":"2022-12-13","published":"2022-03-17"},{"cvss_score":7.5,"headline":"Veeam Backup \u0026 Replication Cloud Connect Missing Authentication for Critical Function","id":"CVE-2023-27532","kev_date_added":"2023-08-22","published":"2023-03-10"},{"cvss_score":10,"headline":"Missing authorization in Backup and Replication","id":"CVE-2026-21666","kev_date_added":null,"published":"2026-03-12"},{"cvss_score":10,"headline":"Missing authorization in Backup and Replication","id":"CVE-2026-21667","kev_date_added":null,"published":"2026-03-12"},{"cvss_score":10,"headline":"Code injection in Backup and Replication","id":"CVE-2026-21669","kev_date_added":null,"published":"2026-03-12"}],"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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-12-04","vendors":["Veeam"]},"summary":"Operators can expose saved plaintext credentials by adding a malicious host, leading to credential theft and potential account takeover.","url":"https://insights.sbomify.com/CVE-2024-42457/"}