{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2017-12425 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2017-12425 is a high-severity vulnerability in n/a, published on 4 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-12425 and fix it if it is affected.\n\nWhat it is: CVE-2017-12425 is a high-severity vulnerability in n/a, published on 4 Aug 2017. 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-2017-12425 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-2017-12425/ (Markdown: https://insights.sbomify.com/CVE-2017-12425/index.md)","id":"CVE-2017-12425","markdown":"https://insights.sbomify.com/CVE-2017-12425/index.md","name":"CVE-2017-12425","record":{"aliases":["ALPINE-CVE-2017-12425","CVE-2017-1000123","DEBIAN-CVE-2017-12425","DSA-3924-1","GHSA-jhqh-84v8-3cw2","MGASA-2017-0253","UBUNTU-CVE-2017-12425"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Varnish HTTP Cache","requires_auth":"none","summary":"An integer overflow in Varnish HTTP Cache allows attackers to crash the worker process via invalid requests, causing a denial of service.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"varnish","vendor":"varnish-cache"},{"product":"varnish_cache","vendor":"varnish-software"},{"product":"varnish_cache","vendor":"varnish_cache_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"}],"description":"An issue was discovered in Varnish HTTP Cache 4.0.1 through 4.0.4, 4.1.0 through 4.1.7, 5.0.0, and 5.1.0 through 5.1.2. A wrong if statement in the varnishd source code means that particular invalid requests from the client can trigger an assert, related to an Integer Overflow. This causes the varnishd worker process to abort and restart, losing the cached contents in the process. An attacker can therefore crash the varnishd worker process on demand and effectively keep it from serving content - a Denial-of-Service attack. The specific source-code filename containing the incorrect statement varies across releases.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Integer overflow in n/a","id":"CVE-2017-12425","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2017"},"n_packages":0,"n_references":6,"next":{"headline":"Command injection in n/a","id":"CVE-2017-12426"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2017-12424"},"products":["n/a"],"published":"2017-08-04","related":[{"cvss_score":5,"headline":"Denial of service in n/a","id":"CVE-2013-4484","kev_date_added":null,"published":"2013-11-01"}],"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":["n/a"]},"summary":"An integer overflow in Varnish HTTP Cache allows attackers to crash the worker process via invalid requests, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2017-12425/"}