How severe is GHSA-2ggq-vfcp-gwhj?

GHSA-2ggq-vfcp-gwhj has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-2ggq-vfcp-gwhj?

GHSA-2ggq-vfcp-gwhj affects the following packages: @hapi/boom (npm). Ecosystems affected: npm.

How do I fix GHSA-2ggq-vfcp-gwhj?

Update @hapi/boom to 0.3.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2ggq-vfcp-gwhj is resolved across your whole dependency graph.

How do I detect GHSA-2ggq-vfcp-gwhj in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @hapi/boom. 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-2ggq-vfcp-gwhj 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-2ggq-vfcp-gwhj?

O3 pinpoints whether GHSA-2ggq-vfcp-gwhj 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-2ggq-vfcp-gwhj actively exploited in the wild?

No public exploit code has been indexed for GHSA-2ggq-vfcp-gwhj 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.

When was GHSA-2ggq-vfcp-gwhj published, and has it been updated?

GHSA-2ggq-vfcp-gwhj was published on September 4, 2020 and was last updated on October 2, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

MEDIUM severity

GHSA-2ggq-vfcp-gwhj

MEDIUMFix: hapijs/boom@0f8640b

GHSA-2ggq-vfcp-gwhj is a medium-severity (CVSS 6.5) vulnerability in @hapi/boom. O3 Security confirms whether GHSA-2ggq-vfcp-gwhj is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Cross-Site Scripting in @hapi/boom

Published

Sep 4, 2020

Updated

Oct 2, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 2, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

📦@hapi/boom

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

Description

Versions of @hapi/boom prior to 0.3.8 are vulnerable to Cross-Site Scripting (XSS). The package fails to properly escape error messages, which may allow attackers to execute arbitrary JavaScript in a victim's browser.

Recommendation

Upgrade to version 0.3.8 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@hapi/boom`	all versions	0.3.8

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @hapi/boom. 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 @hapi/boom to 0.3.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2ggq-vfcp-gwhj 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-2ggq-vfcp-gwhj 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-2ggq-vfcp-gwhj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions of `@hapi/boom` prior to 0.3.8 are vulnerable to Cross-Site Scripting (XSS). The package fails to properly escape error messages, which may allow attackers to execute arbitrary JavaScript in a victim's browser. ## Recommendation Upgrade to version 0.3.8 or later.

O3 Security · Impact-Aware SCA

Is GHSA-2ggq-vfcp-gwhj in your dependencies?

O3 detects GHSA-2ggq-vfcp-gwhj across npm 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