{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-19035 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2019-19035 is a medium-severity memory corruption vulnerability in n/a, published on 17 Nov 2019. 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-2019-19035 and fix it if it is affected.\n\nWhat it is: CVE-2019-19035 is a medium-severity memory corruption vulnerability in n/a, published on 17 Nov 2019. 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-2019-19035 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-19035/ (Markdown: https://insights.sbomify.com/CVE-2019-19035/index.md)","id":"CVE-2019-19035","markdown":"https://insights.sbomify.com/CVE-2019-19035/index.md","name":"CVE-2019-19035","record":{"aliases":["DEBIAN-CVE-2019-19035","GHSA-m4jc-jx4g-52vw","UBUNTU-CVE-2019-19035"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"JPEG image viewer","requires_auth":"none","summary":"An attacker can cause a denial of service by tricking a user into opening a specially crafted JPEG file with jhead.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"jhead","vendor":"jhead_project"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"jhead 3.03 is affected by: heap-based buffer over-read. The impact is: Denial of service. The component is: ReadJpegSections and process_SOFn in jpgfile.c. The attack vector is: Open a specially crafted JPEG file.","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-2019-19035","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2019"},"n_packages":0,"n_references":4,"next":{"headline":"Null dereference in n/a","id":"CVE-2019-19036"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2019-19034"},"products":["n/a"],"published":"2019-11-17","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2022-28550","kev_date_added":null,"published":"2023-06-13"},{"cvss_score":7.8,"headline":"Use after free in n/a","id":"CVE-2025-44906","kev_date_added":null,"published":"2025-05-30"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2021-28277","kev_date_added":null,"published":"2022-03-23"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2021-28278","kev_date_added":null,"published":"2022-03-23"},{"cvss_score":7.8,"headline":"Memory corruption in jhead","id":"CVE-2021-3496","kev_date_added":null,"published":"2021-04-22"},{"cvss_score":7.8,"headline":"Other in n/a","id":"CVE-2018-16554","kev_date_added":null,"published":"2018-09-16"},{"cvss_score":7.8,"headline":"Integer overflow in n/a","id":"CVE-2018-17088","kev_date_added":null,"published":"2018-09-16"}],"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":"An attacker can cause a denial of service by tricking a user into opening a specially crafted JPEG file with jhead.","url":"https://insights.sbomify.com/CVE-2019-19035/"}