{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-4973 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-4973 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-4973 is a high-severity memory corruption vulnerability in n/a, published on 7 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-2016-4973 and fix it if it is affected.\n\nWhat it is: CVE-2016-4973 is a high-severity memory corruption vulnerability in n/a, published on 7 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-2016-4973 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-2016-4973/ (Markdown: https://insights.sbomify.com/CVE-2016-4973/index.md)","id":"CVE-2016-4973","markdown":"https://insights.sbomify.com/CVE-2016-4973/index.md","name":"CVE-2016-4973","record":{"aliases":["DEBIAN-CVE-2016-4973","ECHO-a343-3595-94e7","GHSA-fxx4-jm8v-4948","UBUNTU-CVE-2016-4973"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"GCC libssp library","requires_auth":"low_privilege","summary":"Local attackers can exploit buffer overflows in binaries using GCC libssp due to missing Object Size Checking, potentially executing arbitrary code.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"libssp","vendor":"gnu"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/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":"Binaries compiled against targets that use the libssp library in GCC for stack smashing protection (SSP) might allow local users to perform buffer overflow attacks by leveraging lack of the Object Size Checking feature.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Memory corruption in n/a","id":"CVE-2016-4973","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2016"},"n_packages":0,"n_references":3,"next":{"headline":"Improper Input Validation in Apache Qpid AMQP 0-x JMS","id":"CVE-2016-4974"},"packages":[],"prev":{"headline":"OpenStack Murano Code Execution","id":"CVE-2016-4972"},"products":["n/a"],"published":"2017-06-07","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-06","vendors":["n/a"]},"summary":"Local attackers can exploit buffer overflows in binaries using GCC libssp due to missing Object Size Checking, potentially executing arbitrary code.","url":"https://insights.sbomify.com/CVE-2016-4973/"}