{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-23082 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-23082 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-23082 is a high-severity server-side request forgery vulnerability in Veeam Backup for Microsoft Azure, published on 14 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-23082 and fix it if it is affected.\n\nWhat it is: CVE-2025-23082 is a high-severity server-side request forgery vulnerability in Veeam Backup for Microsoft Azure, published on 14 Jan 2025. 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-2025-23082 in the wild and no public exploit code.\n\nAffected product: Veeam Backup for Microsoft Azure. 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-2025-23082/ (Markdown: https://insights.sbomify.com/CVE-2025-23082/index.md)","id":"CVE-2025-23082","markdown":"https://insights.sbomify.com/CVE-2025-23082/index.md","name":"CVE-2025-23082","record":{"aliases":["GHSA-hj9f-h3qv-vpjm"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Veeam Backup for Azure","requires_auth":"none","summary":"Unauthenticated attackers can exploit SSRF in Veeam Backup for Microsoft Azure to send unauthorized requests, enabling network enumeration and facilitating further attacks.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"backup","vendor":"veeam"}],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Veeam Backup for Microsoft Azure is vulnerable to Server-Side Request Forgery (SSRF). This may allow an unauthenticated attacker to send unauthorized requests from the system, potentially leading to network enumeration or facilitating other attacks.","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":"Server-side request forgery in Backup for Microsoft Azure","id":"CVE-2025-23082","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Security feature bypass in Node","id":"CVE-2025-23083"},"packages":[],"prev":{"headline":"Various security vulnerabilities in Extension:DataTransfer","id":"CVE-2025-23081"},"products":["Backup for Microsoft Azure"],"published":"2025-01-14","related":[],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-01-14","vendors":["Veeam"]},"summary":"Unauthenticated attackers can exploit SSRF in Veeam Backup for Microsoft Azure to send unauthorized requests, enabling network enumeration and facilitating further attacks.","url":"https://insights.sbomify.com/CVE-2025-23082/"}