{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-3219 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-3219 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-3219 is a high-severity vulnerability in Acronis True Image, published on 21 Jun 2017. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-3219 and fix it if it is affected.\n\nWhat it is: CVE-2017-3219 is a high-severity vulnerability in Acronis True Image, published on 21 Jun 2017. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-3219 in the wild and no public exploit code.\n\nAffected product: Acronis True Image. 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-2017-3219/ (Markdown: https://insights.sbomify.com/CVE-2017-3219/index.md)","id":"CVE-2017-3219","markdown":"https://insights.sbomify.com/CVE-2017-3219/index.md","name":"CVE-2017-3219","record":{"aliases":["GHSA-67cv-mr76-54w6"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Acronis True Image","requires_auth":"none","summary":"Attackers can intercept HTTP updates and replace them with malicious binaries due to weak MD5 verification, leading to code execution.","user_interaction":"not_required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"certcc","cpe":[{"product":"true_image","vendor":"acronis"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"},{"id":"CWE-311","name":"Missing Encryption of Sensitive Data"}],"description":"Acronis True Image up to and including version 2017 Build 8053 performs software updates using HTTP. Downloaded updates are only verified using a server-provided MD5 hash.","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":"Supply chain in True Image","id":"CVE-2017-3219","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"supply_chain","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"SQL injection in AmosConnect","id":"CVE-2017-3221"},"packages":[],"prev":{"headline":"Security feature bypass in Magician","id":"CVE-2017-3218"},"products":["True Image"],"published":"2017-06-21","related":[{"cvss_score":7.8,"headline":"Path traversal in n/a","id":"CVE-2021-32576","kev_date_added":null,"published":"2021-08-05"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2021-32577","kev_date_added":null,"published":"2021-08-05"},{"cvss_score":7.8,"headline":"Path traversal in n/a","id":"CVE-2021-32578","kev_date_added":null,"published":"2021-08-05"},{"cvss_score":7.8,"headline":"Auth bypass in n/a","id":"CVE-2021-32579","kev_date_added":null,"published":"2021-08-05"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2021-32580","kev_date_added":null,"published":"2021-08-05"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2020-15495","kev_date_added":null,"published":"2021-07-15"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["Acronis"]},"summary":"Attackers can intercept HTTP updates and replace them with malicious binaries due to weak MD5 verification, leading to code execution.","url":"https://insights.sbomify.com/CVE-2017-3219/"}