Path traversal in apimock's file-serving fallback
Historical advisory saved 24 Oct 2026 13:19:54 UTC. The publisher may have updated it since then. Latest advisory.
osv · RUSTSEC-2026-0276
PublishedThe file-serving fallback joined a request-derived path onto the configured response directory and checked only that the result existed, never that it stayed inside that directory. A request containing a raw `..` segment could read any file readable by the process, returned with HTTP 200. Read-only: no write, no code execution. On the 4.x line `apimock` is a single crate containing the serving code. Fixed in 4.8.1 by canonicalising each resolved path and rejecting anything outside its base directory. **apimock 5.0.0 and later are not affected by this advisory.** From 5.0.0 the serving code moved to the `apimock-server` crate, which `apimock` depends on; that crate carries its own advisory for the same issue, fixed in 5.19.1.
- Source published
- 26 Aug 2026 12:00:00 UTC
- Source modified
- 2 Sep 2026 09:10:39 UTC
- Saved here
- 24 Oct 2026 13:19:54 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V4 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N