Hoverfly allows an arbitrary file read in the /api/v2/simulation endpoint (GHSL-2023-274)
CVE-2024-45388GHSA-6xx4-x46f-f897
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/spectolabs/hoverfly 1.10.3), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go github.com/spectolabs/hoverfly
- Affected
- < 1.10.3
- Fixed in
- 1.10.3
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-6xx4-x46f-f897 lists affected ranges: Go github.com/spectolabs/hoverfly >=0 <1.10.3
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source
- EPSS
- CVE-2024-45388: 55.57% estimated exploitation activity in the next 30 days; percentile 99.04 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Details The /api/v2/simulation POST handler allows users to create new simulation views from the contents of a user-specified file. This feature can be abused by an attacker to read arbitrary files from the Hoverfly server. Note that, although the code prevents absolute paths from being specified, an attacker can escape out of the hf.Cfg.ResponsesBodyFilesPath base path by using ../ segments and reach any arbitrary files. This issue was found using the Uncontrolled data used in path expression CodeQL query for python. Proof of Concept Send the following POST request to read the /etc/passwd file: Response will contain the Hoverfly's server /etc/passwd Impact This issue may lead to Information Disclosure. Remediation The code is preventing absolute paths from being read. Make sure the final path (filepath.Join(hf.Cfg.ResponsesBodyFilesPath, filePath)) is contained within the expected base path (filepath.Join(hf.Cfg.ResponsesBodyFilesPath, "/"))
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-6xx4-x46f-f897
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2024-45388 Advisory: Hoverfly allows an arbitrary file read in the `/api/v2/simulation` endpoint (`GHSL-2023-274`) IDs: CVE-2024-45388, GHSA-6xx4-x46f-f897 Record: https://patchnext.com/advisories/cve-2024-45388 (revision 1, source checked 26 Oct 2026, 15:05 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 8.7) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/spectolabs/hoverfly 1.10.3. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/spectolabs/hoverfly: affected < 1.10.3; fixed in 1.10.3 ## Suggested inspection (read-only) - Go github.com/spectolabs/hoverfly: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/spectolabs/hoverfly. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-6xx4-x46f-f897 (GitHub-reviewed advisory GHSA-6xx4-x46f-f897 lists affected ranges: Go github.com/spectolabs/hoverfly >=0 <1.10.3) Commands are suggestions: review each one before running it.
Loading voting…