{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-5318 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2016-5318 is a medium-severity memory corruption vulnerability in Libtiff Libtiff, published on 20 Jan 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2016-5318 and fix it if it is affected.\n\nWhat it is: CVE-2016-5318 is a medium-severity memory corruption vulnerability in Libtiff Libtiff, published on 20 Jan 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2016-5318 in the wild and no public exploit code.\n\nAffected product: Libtiff Libtiff. 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-5318/ (Markdown: https://insights.sbomify.com/CVE-2016-5318/index.md)","id":"CVE-2016-5318","markdown":"https://insights.sbomify.com/CVE-2016-5318/index.md","name":"CVE-2016-5318","record":{"aliases":["DEBIAN-CVE-2016-5318","GHSA-hqx5-9h4v-xwm4","UBUNTU-CVE-2016-5318"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"libtiff image library","requires_auth":"none","summary":"Remote attackers can crash applications using libtiff by sending crafted TIFF files due to a stack-based buffer overflow.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"libtiff","vendor":"libtiff"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"Stack-based buffer overflow in the _TIFFVGetField function in libtiff 4.0.6 and earlier allows remote attackers to crash the application via a crafted tiff.","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-2016-5318","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"libtiff:libtiff","products":["libtiff:libtiff"],"type":"memory_corruption","year":"2016"},"n_packages":0,"n_references":5,"next":{"headline":"Memory corruption in n/a","id":"CVE-2016-5319"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2016-5317"},"products":["n/a"],"published":"2017-01-20","related":[{"cvss_score":10,"headline":"Integer overflow in n/a","id":"CVE-2004-1308","kev_date_added":null,"published":"2004-12-22"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2004-0929","kev_date_added":null,"published":"2004-10-26"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2025-61144","kev_date_added":null,"published":"2026-02-23"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2016-9533","kev_date_added":null,"published":"2016-11-22"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2016-9534","kev_date_added":null,"published":"2016-11-22"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2016-9535","kev_date_added":null,"published":"2016-11-22"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2016-9536","kev_date_added":null,"published":"2016-11-22"}],"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":"Remote attackers can crash applications using libtiff by sending crafted TIFF files due to a stack-based buffer overflow.","url":"https://insights.sbomify.com/CVE-2016-5318/"}