Path traversal in apimock-server'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-0277
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. Exposure depends on the bind address. The default is `127.0.0.1`; deployments binding `0.0.0.0` or a LAN address are reachable from the network. Most HTTP clients normalise `..` away before sending, so reaching it requires a client that does not. All published versions before 5.19.1 are affected. Fixed in 5.19.1 by canonicalising each resolved path and rejecting anything outside its base directory. **This advisory also covers `apimock` 5.x**, which depends on `apimock-server`. `apimock` 4.x predates the crate split and carries its own advisory for the same issue, fixed in 4.8.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