{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-22564 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-22564 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-22564 is a medium-severity memory corruption vulnerability in Google LLC libjxl, published on 1 Nov 2021. 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-2021-22564 and fix it if it is affected.\n\nWhat it is: CVE-2021-22564 is a medium-severity memory corruption vulnerability in Google LLC libjxl, published on 1 Nov 2021. 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-2021-22564 in the wild and no public exploit code.\n\nAffected product: Google LLC 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-2021-22564/ (Markdown: https://insights.sbomify.com/CVE-2021-22564/index.md)","id":"CVE-2021-22564","markdown":"https://insights.sbomify.com/CVE-2021-22564/index.md","name":"CVE-2021-22564","record":{"aliases":["GHSA-fj6w-9c57-3287"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"JPEG XL decoder library","requires_auth":"low_privilege","summary":"An out-of-bounds copy in the libjxl decoder allows attackers to cause memory corruption and potential code execution via crafted JPEG XL images.","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":4.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"description":"For certain valid JPEG XL images with a size slightly larger than an integer number of groups (256x256 pixels) when processing the groups out of order the decoder can perform an out of bounds copy of image pixels from an image buffer in the heap to another. This copy can occur when processing the right or bottom edges of the image, but only when groups are processed in certain order. Groups can be processed out of order in multi-threaded decoding environments with heavy thread load but also with images that contain the groups in an arbitrary order in the file. It is recommended to upgrade past 0.6.0 or patch with https://github.com/libjxl/libjxl/pull/775","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":"Out of bounds Copy in Libjxl in large image groups","id":"CVE-2021-22564","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Insufficient Granularity of Access Control in GAEN Notification Server","id":"CVE-2021-22565"},"packages":[],"prev":{"headline":"Memory Overread in libjxl","id":"CVE-2021-22563"},"products":["libjxl"],"published":"2021-11-01","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["Google LLC"]},"summary":"An out-of-bounds copy in the libjxl decoder allows attackers to cause memory corruption and potential code execution via crafted JPEG XL images.","url":"https://insights.sbomify.com/CVE-2021-22564/"}