How severe is GHSA-q9rr-h3hx-m87g?

No CVSS score has been assigned to GHSA-q9rr-h3hx-m87g yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-q9rr-h3hx-m87g?

GHSA-q9rr-h3hx-m87g affects the following packages: github.com/bunkerity/bunkerweb (Go). Ecosystems affected: Go.

How do I fix GHSA-q9rr-h3hx-m87g?

Update github.com/bunkerity/bunkerweb to 1.5.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q9rr-h3hx-m87g is resolved across your whole dependency graph.

How do I detect GHSA-q9rr-h3hx-m87g in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/bunkerity/bunkerweb. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-q9rr-h3hx-m87g if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-q9rr-h3hx-m87g?

O3 pinpoints whether GHSA-q9rr-h3hx-m87g is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-q9rr-h3hx-m87g actively exploited in the wild?

No public exploit code has been indexed for GHSA-q9rr-h3hx-m87g yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-q9rr-h3hx-m87g?

GHSA-q9rr-h3hx-m87g is classified as Open Redirect (CWE-601). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-q9rr-h3hx-m87g published, and has it been updated?

GHSA-q9rr-h3hx-m87g was published on December 2, 2024 and was last updated on December 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-q9rr-h3hx-m87g

GHSA-q9rr-h3hx-m87g is a Open Redirect vulnerability in github.com/bunkerity/bunkerweb. O3 Security confirms whether GHSA-q9rr-h3hx-m87g is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

BunkerWeb has Open Redirect Vulnerability in Loading Page

Also known asCVE-2024-53264GO-2024-3294

Published

Dec 2, 2024

Updated

Dec 2, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐹github.com/bunkerity/bunkerweb

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

Summary:

A open redirect vulnerability exists in the loading endpoint, allowing attackers to redirect authenticated users to arbitrary external URLs via the "next" parameter.

Details:

The loading endpoint accepts and uses an unvalidated "next" parameter for redirects:

PoC:

Visit: /loading?next=https://google.com while authenticated. The page will redirect to google.com.

Impact:

This vulnerability could be used in phishing attacks by redirecting users from a legitimate application URL to malicious sites.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/bunkerity/bunkerweb`	all versions	1.5.11

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/bunkerity/bunkerweb. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/bunkerity/bunkerweb to 1.5.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q9rr-h3hx-m87g is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-q9rr-h3hx-m87g is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-q9rr-h3hx-m87g. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary: A open redirect vulnerability exists in the loading endpoint, allowing attackers to redirect authenticated users to arbitrary external URLs via the "next" parameter. ### Details: The loading endpoint accepts and uses an unvalidated "next" parameter for redirects: ### PoC: Visit: `/loading?next=https://google.com` while authenticated. The page will redirect to google.com. ### Impact: This vulnerability could be used in phishing attacks by redirecting users from a legitimate application URL to malicious sites.

O3 Security · Impact-Aware SCA

Is GHSA-q9rr-h3hx-m87g in your dependencies?

O3 detects GHSA-q9rr-h3hx-m87g across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works