{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-6949 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2017-6949 is a high-severity vulnerability in n/a, published on 16 Mar 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-6949 and fix it if it is affected.\n\nWhat it is: CVE-2017-6949 is a high-severity vulnerability in n/a, published on 16 Mar 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-6949 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-6949/ (Markdown: https://insights.sbomify.com/CVE-2017-6949/index.md)","id":"CVE-2017-6949","markdown":"https://insights.sbomify.com/CVE-2017-6949/index.md","name":"CVE-2017-6949","record":{"aliases":["CLEANSTART-2023-LZ34592","DEBIAN-CVE-2017-6949","DLA-908-1","GHSA-mg7g-v2j9-85r8","UBUNTU-CVE-2017-6949"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"CHICKEN Scheme library","requires_auth":"none","summary":"Attackers can trigger a buffer overflow or segfault in CHICKEN Scheme by exploiting unsanitized vector size arguments in unmanaged memory allocation.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"chicken","vendor":"call-cc"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"An issue was discovered in CHICKEN Scheme through 4.12.0. When using a nonstandard CHICKEN-specific extension to allocate an SRFI-4 vector in unmanaged memory, the vector size would be used in unsanitised form as an argument to malloc(). With an unexpected size, the impact may have been a segfault or buffer overflow.","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-6949","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Code injection in n/a","id":"CVE-2017-6950"},"packages":[],"prev":{"headline":"Drupal external link injection vulnerability","id":"CVE-2017-6932"},"products":["n/a"],"published":"2017-03-16","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2022-45145","kev_date_added":null,"published":"2022-12-10"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2014-6310","kev_date_added":null,"published":"2019-11-22"},{"cvss_score":9.8,"headline":"Denial of service in chicken","id":"CVE-2012-6125","kev_date_added":null,"published":"2019-10-31"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2016-6830","kev_date_added":null,"published":"2017-01-10"},{"cvss_score":8.8,"headline":"Command injection in chicken","id":"CVE-2013-2024","kev_date_added":null,"published":"2019-10-31"},{"cvss_score":8.8,"headline":"Memory corruption in chicken","id":"CVE-2013-2075","kev_date_added":null,"published":"2019-10-31"}],"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":"Attackers can trigger a buffer overflow or segfault in CHICKEN Scheme by exploiting unsanitized vector size arguments in unmanaged memory allocation.","url":"https://insights.sbomify.com/CVE-2017-6949/"}