NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹 Go
Not in CISA KEV

Initial debug-host handler implementation could leak information and facilitate denial of serviceGHSA-x477-fq37-q5wr

Fix: fortio/proxy#38

GHSA-x477-fq37-q5wr is a security vulnerability in fortio.org/proxy. A fix is available for fortio.org/proxy — see the affected versions and patch details below.

Also known asGO-2023-1524
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Aug 20, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐹fortio.org/proxy

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

version 1.5.0 and 1.6.0 when using the new debug-host feature could expose unnecessary information about the host

Patches

Use 1.6.1 or newer

Workarounds

Downgrade to 1.4.0 or set debug-host to empty

References

https://github.com/fortio/proxy/pull/38

Q&A https://github.com/fortio/proxy/discussions

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gofortio.org/proxy≥ 1.5.0&&< 1.6.11.6.1go get fortio.org/proxy@v1.6.1

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fortio.org/proxy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update fortio.org/proxy to 1.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x477-fq37-q5wr is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact version 1.5.0 and 1.6.0 when using the new `debug-host` feature could expose unnecessary information about the host ### Patches Use 1.6.1 or newer ### Workarounds Downgrade to 1.4.0 or set `debug-host` to empty ### References https://github.com/fortio/proxy/pull/38 Q&A https://github.com/fortio/proxy/discussions
O3 Security · Impact-Aware SCA

Is GHSA-x477-fq37-q5wr in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
Initial debug-host handler implementation could leak…