{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-17264 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-17264 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-17264 is a low-severity memory corruption vulnerability in n/a, published on 6 Oct 2019. 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-2019-17264 and fix it if it is affected.\n\nWhat it is: CVE-2019-17264 is a low-severity memory corruption vulnerability in n/a, published on 6 Oct 2019. 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-2019-17264 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-2019-17264/ (Markdown: https://insights.sbomify.com/CVE-2019-17264/index.md)","id":"CVE-2019-17264","markdown":"https://insights.sbomify.com/CVE-2019-17264/index.md","name":"CVE-2019-17264","record":{"aliases":["DEBIAN-CVE-2019-17264","GHSA-qvh2-jh54-687w"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"liblnk library","requires_auth":"low_privilege","summary":"A heap-based buffer over-read in liblnk allows attackers to cause denial of service or disclose sensitive memory contents via crafted files.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"liblnk","vendor":"liblnk_project"}],"cvss":{"score":3.3,"severity":"low","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-682","name":"Incorrect Calculation"},{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"In libyal liblnk before 20191006, liblnk_location_information_read_data in liblnk_location_information.c has a heap-based buffer over-read because an incorrect variable name is used for a certain offset. NOTE: the vendor has disputed this as described in the GitHub issue","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-2019-17264","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2019-17266"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2019-17263"},"products":["n/a"],"published":"2019-10-06","related":[{"cvss_score":5.5,"headline":"Information disclosure in n/a","id":"CVE-2018-12096","kev_date_added":null,"published":"2018-06-19"},{"cvss_score":5.5,"headline":"Information disclosure in n/a","id":"CVE-2018-12097","kev_date_added":null,"published":"2018-06-19"},{"cvss_score":5.5,"headline":"Information disclosure in n/a","id":"CVE-2018-12098","kev_date_added":null,"published":"2018-06-19"},{"cvss_score":3.3,"headline":"Memory corruption in n/a","id":"CVE-2019-17401","kev_date_added":null,"published":"2019-10-09"}],"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":"A heap-based buffer over-read in liblnk allows attackers to cause denial of service or disclose sensitive memory contents via crafted files.","url":"https://insights.sbomify.com/CVE-2019-17264/"}