{"answers":{"affected":"3 open source packages ship an affected version, including check-jsonschema.","exploited":"There is no known exploitation of CVE-2024-53848 in the wild and no public exploit code.","fix":"Upgrade check-jsonschema to 0.30.0 or later.","what":"CVE-2024-53848 is a high-severity vulnerability in python-jsonschema check-jsonschema, published on 29 Nov 2024. 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-2024-53848 and fix it if it is affected.\n\nWhat it is: CVE-2024-53848 is a high-severity vulnerability in python-jsonschema check-jsonschema, published on 29 Nov 2024. 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-2024-53848 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- check-jsonschema (PyPI): affected all versions; fixed in 0.30.0\n- check-jsonschema (PyPI): affected all versions; fixed in 0.30.0\n- check-jsonschema (PyPI): affected all versions; fixed in 0.30.0\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-2024-53848/ (Markdown: https://insights.sbomify.com/CVE-2024-53848/index.md)","id":"CVE-2024-53848","markdown":"https://insights.sbomify.com/CVE-2024-53848/index.md","name":"CVE-2024-53848","record":{"aliases":["GHSA-q6mv-284r-mp36","PYSEC-2026-1245"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Python schema validator","requires_auth":"none","summary":"Attackers can poison the schema cache to bypass validation checks, allowing malicious data to pass validation in check-jsonschema.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-349","name":"Acceptance of Extraneous Untrusted Data With Trusted Data"}],"description":"check-jsonschema is a CLI and set of pre-commit hooks for jsonschema validation. The default cache strategy uses the basename of a remote schema as the name of the file in the cache, e.g. `https://example.org/schema.json` will be stored as `schema.json`. This naming allows for conflicts. If an attacker can get a user to run `check-jsonschema` against a malicious schema URL, e.g., `https://example.evil.org/schema.json`, they can insert their own schema into the cache and it will be picked up and used instead of the appropriate schema. Such a cache confusion attack could be used to allow data to pass validation which should have been rejected. This issue has been patched in version 0.30.0. All users are advised to upgrade. A few workarounds exist: 1. Users can use `--no-cache` to disable caching. 2. Users can use `--cache-filename` to select filenames for use in the cache, or to ensure that other usages do not overwrite the cached schema. (Note: this flag is being deprecated as part of the remediation effort.) 3. Users can explicitly download the schema before use as a local file, as in `curl -LOs https://example.org/schema.json; check-jsonschema --schemafile ./schema.json`","ecosystems":["PyPI"],"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":"check-jsonschema default caching for remote schemas allows for cache confusion","id":"CVE-2024-53848","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"other","year":"2024"},"n_packages":3,"n_references":2,"next":{"headline":"Several stack buffer overflows and pointer overflows in editorconfig-core-c","id":"CVE-2024-53849"},"packages":[{"ecosystem":"PyPI","fixed":["0.30.0"],"introduced":["0"],"last_affected":[],"package":"check-jsonschema","purl":null,"source":"GHSA-q6mv-284r-mp36"},{"ecosystem":"PyPI","fixed":["0.30.0"],"introduced":["0"],"last_affected":[],"package":"check-jsonschema","purl":"pkg:pypi/check-jsonschema","source":"GHSA-q6mv-284r-mp36"},{"ecosystem":"PyPI","fixed":["0.30.0"],"introduced":["0"],"last_affected":[],"package":"check-jsonschema","purl":"pkg:pypi/check-jsonschema","source":"PYSEC-2026-1245"}],"prev":{"headline":"Trix vulnerable to Cross-site Scripting on copy \u0026 paste","id":"CVE-2024-53847"},"products":["check-jsonschema"],"published":"2024-11-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":"2024-12-02","vendors":["python-jsonschema"]},"summary":"Attackers can poison the schema cache to bypass validation checks, allowing malicious data to pass validation in check-jsonschema.","url":"https://insights.sbomify.com/CVE-2024-53848/"}