{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-0645 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2023-0645 is a medium-severity memory corruption vulnerability in Libjxl, published on 11 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-0645 and fix it if it is affected.\n\nWhat it is: CVE-2023-0645 is a medium-severity memory corruption vulnerability in Libjxl, published on 11 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-0645 in the wild and no public exploit code.\n\nAffected product: Libjxl. 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-2023-0645/ (Markdown: https://insights.sbomify.com/CVE-2023-0645/index.md)","id":"CVE-2023-0645","markdown":"https://insights.sbomify.com/CVE-2023-0645/index.md","name":"CVE-2023-0645","record":{"aliases":["DEBIAN-CVE-2023-0645","GHSA-378h-jm2h-7wrm","UBUNTU-CVE-2023-0645"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"JPEG XL library","requires_auth":"low_privilege","summary":"An attacker can cause an out-of-bounds read in libjxl via a crafted file, potentially leading to crashes or information disclosure.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Google","cpe":[{"product":"libjxl","vendor":"libjxl_project"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"An out of bounds read exists in libjxl. An attacker using a specifically crafted file could cause an out of bounds read in the exif handler. We recommend upgrading to version 0.8.1 or past commit  https://github.com/libjxl/libjxl/pull/2101/commits/d95b050c1822a5b1ede9e0dc937e43fca1b10159 https://github.com/libjxl/libjxl/pull/2101/commits/d95b050c1822a5b1ede9e0dc937e43fca1b10159","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":"Out of Bounds read in libjxl","id":"CVE-2023-0645","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"dst-admin cavesConsole command injection","id":"CVE-2023-0646"},"packages":[],"prev":{"headline":"PushAssist \u003c= 3.0.8 - Reflected Cross-Site Scripting","id":"CVE-2023-0644"},"products":["Libjxl"],"published":"2023-04-11","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2021-27804","kev_date_added":null,"published":"2021-03-02"},{"cvss_score":8.7,"headline":"libjxl: Out-of-bounds write in grayscale color transformation when using LCMS2","id":"CVE-2026-1837","kev_date_added":null,"published":"2026-02-11"},{"cvss_score":7.5,"headline":"Integer overflow in n/a","id":"CVE-2023-35790","kev_date_added":null,"published":"2023-06-16"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2021-36691","kev_date_added":null,"published":"2021-08-30"},{"cvss_score":6.9,"headline":"Out of Bounds Memory Read/Write in libjxl","id":"CVE-2024-11403","kev_date_added":null,"published":"2024-11-25"},{"cvss_score":6.9,"headline":"Resource exhaustion via Stack overflow in libjxl","id":"CVE-2024-11498","kev_date_added":null,"published":"2024-11-25"},{"cvss_score":6.5,"headline":"Denial of service in n/a","id":"CVE-2022-34000","kev_date_added":null,"published":"2022-06-19"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-29","vendors":["Libjxl"]},"summary":"An attacker can cause an out-of-bounds read in libjxl via a crafted file, potentially leading to crashes or information disclosure.","url":"https://insights.sbomify.com/CVE-2023-0645/"}