{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-16171 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-16171 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-16171 is a medium-severity server-side request forgery vulnerability in n/a, published on 21 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-16171 and fix it if it is affected.\n\nWhat it is: CVE-2020-16171 is a medium-severity server-side request forgery vulnerability in n/a, published on 21 Sep 2020. 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-2020-16171 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2020-16171/ (Markdown: https://insights.sbomify.com/CVE-2020-16171/index.md)","id":"CVE-2020-16171","markdown":"https://insights.sbomify.com/CVE-2020-16171/index.md","name":"CVE-2020-16171","record":{"aliases":["GHSA-2347-fp75-m9xc"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Acronis Cyber Backup","requires_auth":"none","summary":"Attackers can exploit a custom header in Acronis Cyber Backup API endpoints to perform Server-Side Request Forgery against internal localhost services.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"cyber_backup","vendor":"acronis"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"An issue was discovered in Acronis Cyber Backup before 12.5 Build 16342. Some API endpoints on port 9877 under /api/ams/ accept an additional custom Shard header. The value of this header is afterwards used in a separate web request issued by the application itself. This can be abused to conduct SSRF attacks against otherwise unreachable Acronis services that are bound to localhost such as the NotificationService on 127.0.0.1:30572.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2020-11-27","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2020-11-27","kind":"exploitdb","ref":"49113","stars":null,"title":"Acronis Cyber Backup 12.5 Build 16341 - Unauthenticated SSRF"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Server-side request forgery in n/a","id":"CVE-2020-16171","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2020-16186"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2020-16170"},"products":["n/a"],"published":"2020-09-21","related":[{"cvss_score":9.3,"headline":"Information disclosure in Acronis Cyber Backup 12.5","id":"CVE-2022-30995","kev_date_added":null,"published":"2023-05-03"},{"cvss_score":9.3,"headline":"Privilege escalation in Acronis Cyber Backup 12.5","id":"CVE-2022-3405","kev_date_added":null,"published":"2023-05-03"},{"cvss_score":7.8,"headline":"Privilege escalation in Cyber Backup","id":"CVE-2020-10138","kev_date_added":null,"published":"2020-10-21"}],"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":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can exploit a custom header in Acronis Cyber Backup API endpoints to perform Server-Side Request Forgery against internal localhost services.","url":"https://insights.sbomify.com/CVE-2020-16171/"}