{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2008-3196 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2008-3196 is a high-severity memory corruption vulnerability in n/a, published on 16 Jul 2008. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2008-3196 and fix it if it is affected.\n\nWhat it is: CVE-2008-3196 is a high-severity memory corruption vulnerability in n/a, published on 16 Jul 2008. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2008-3196 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-2008-3196/ (Markdown: https://insights.sbomify.com/CVE-2008-3196/index.md)","id":"CVE-2008-3196","markdown":"https://insights.sbomify.com/CVE-2008-3196/index.md","name":"CVE-2008-3196","record":{"aliases":["DEBIAN-CVE-2008-3196","GHSA-8x9m-rr2c-2g59"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Yacc parser generator","requires_auth":"none","summary":"Attackers can trigger an out-of-bounds stack access in Yacc via crafted grammar rules, potentially causing crashes or code execution.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"yacc","vendor":"yacc"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:N/A:C","version":"2.0"},"cwes":[{"id":"CWE-399","name":null}],"description":"skeleton.c in yacc does not properly handle reduction of a rule with an empty right hand side, which allows context-dependent attackers to cause an out-of-bounds stack access when the yacc stack pointer points to the end of the stack.","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":"Memory corruption in n/a","id":"CVE-2008-3196","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2008"},"n_packages":0,"n_references":4,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2008-3197"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2008-3195"},"products":["n/a"],"published":"2008-07-16","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Attackers can trigger an out-of-bounds stack access in Yacc via crafted grammar rules, potentially causing crashes or code execution.","url":"https://insights.sbomify.com/CVE-2008-3196/"}