check-jsonschema
Affected
- introduced
0, fixed0.30.0(ecosystem)
Fixed versions
0.30.0
Fix
- Fixed version
0.30.0pip install --upgrade check-jsonschema==0.30.0
Advisory
Also known as: CVE-2024-53848, GHSA-q6mv-284r-mp36
check-jsonschema default caching for remote schemas allows for cache confusion
Impact
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.
Patches
A patch is in progress but has not yet been released.
Workarounds
--no-cache to disable caching.--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.)curl -LOs https://example.org/schema.json; check-jsonschema --schemafile ./schema.jsonHigh Basis: CVSS v3 score 7.1, vector CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N
0, fixed 0.30.0 (ecosystem)0.30.0
0.30.0pip install --upgrade check-jsonschema==0.30.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: PyPA Advisory Database · CC BY 4.0