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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-2ggq-vfcp-gwhj if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

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

Cross-Site Scripting in @hapi/boomGHSA-2ggq-vfcp-gwhj

MEDIUMFix: hapijs/boom@0f8640b

GHSA-2ggq-vfcp-gwhj is a medium-severity (CVSS 6.5) vulnerability in @hapi/boom. A fix is available for @hapi/boom — see the affected versions and patch details below.

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

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

3Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@hapi/boomnpm

5.4Mdownloads / week

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`npm install @hapi/boom@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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

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?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works