Advisory

GHSA-q6mv-284r-mp36

Also known as: CVE-2024-53848, PYSEC-2026-1245

Summary

check-jsonschema default caching for remote schemas allows for cache confusion

Details

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

  • Users can use --no-cache to disable caching.
  • 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.)
  • 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

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2024-12-02 17:29 UTC
Modified
2026-07-07 17:56 UTC

Affected packages and fixes

check-jsonschema

PyPI · All systems

Affected

  • introduced 0, fixed 0.30.0 (ecosystem)

Fixed versions

0.30.0

Fix

  • Fixed version 0.30.0
    pip install --upgrade check-jsonschema==0.30.0

Fix 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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences