{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-22563 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-22563 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-22563 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-22563 and fix it if it is affected.\n\nWhat it is: CVE-2021-22563 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-22563 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-22563/ (Markdown: https://insights.sbomify.com/CVE-2021-22563/index.md)","id":"CVE-2021-22563","markdown":"https://insights.sbomify.com/CVE-2021-22563/index.md","name":"CVE-2021-22563","record":{"aliases":["GHSA-q2wp-4p9r-fg6g"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"JPEG XL library","requires_auth":"low_privilege","summary":"An out-of-bounds read in libjxl when rendering splines can cause crashes or leak memory, requiring an upgrade to fix.","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-125","name":"Out-of-bounds Read"},{"id":"CWE-126","name":"Buffer Over-read"}],"description":"Invalid JPEG XL images using libjxl can cause an out of bounds access on a std::vector\u003cstd::vector\u003cT\u003e\u003e when rendering splines. The OOB read access can either lead to a segfault, or rendering splines based on other process memory. It is recommended to upgrade past 0.6.0 or patch with https://github.com/libjxl/libjxl/pull/757","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 Overread in libjxl","id":"CVE-2021-22563","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":"Out of bounds Copy in Libjxl in large image groups","id":"CVE-2021-22564"},"packages":[],"prev":{"headline":"Code execution in SLO Generator via YAML Payload","id":"CVE-2021-22557"},"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 read in libjxl when rendering splines can cause crashes or leak memory, requiring an upgrade to fix.","url":"https://insights.sbomify.com/CVE-2021-22563/"}