How severe is GHSA-22h7-7wwg-qmgg?

No CVSS score has been assigned to GHSA-22h7-7wwg-qmgg yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-22h7-7wwg-qmgg?

GHSA-22h7-7wwg-qmgg affects the following packages: @hapi/hoek (npm), @hapi/hoek (npm). Ecosystems affected: npm.

How do I fix GHSA-22h7-7wwg-qmgg?

Update @hapi/hoek to 8.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-22h7-7wwg-qmgg is resolved across your whole dependency graph.

How do I detect GHSA-22h7-7wwg-qmgg in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @hapi/hoek. 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-22h7-7wwg-qmgg 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-22h7-7wwg-qmgg?

O3 pinpoints whether GHSA-22h7-7wwg-qmgg 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-22h7-7wwg-qmgg actively exploited in the wild?

No public exploit code has been indexed for GHSA-22h7-7wwg-qmgg 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-22h7-7wwg-qmgg published, and has it been updated?

GHSA-22h7-7wwg-qmgg was published on September 4, 2020 and was last updated on August 31, 2020. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-22h7-7wwg-qmgg

GHSA-22h7-7wwg-qmgg is a remote code execution vulnerability in @hapi/hoek. O3 Security confirms whether GHSA-22h7-7wwg-qmgg is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Prototype Pollution in @hapi/hoek

Published

Sep 4, 2020

Updated

Aug 31, 2020

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

📦@hapi/hoek📦@hapi/hoek

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/hoek prior to 8.5.1 and 9.0.3 are vulnerable to Prototype Pollution. The clone function fails to prevent the modification of the Object prototype when passed specially-crafted input. Attackers may use this to change existing properties that exist in all objects, which may lead to Denial of Service or Remote Code Execution in specific circumstances.
This issue does not affect hapi applications since the framework protects against such malicious inputs. Applications that use @hapi/hoek outside of the hapi ecosystem may be vulnerable.

Recommendation

Update to version 8.5.1, 9.0.3 or later.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@hapi/hoek`	≥ 8.3.2&&< 8.5.1	8.5.1
📦npm	`@hapi/hoek`	≥ 9.0.0&&< 9.0.3	9.0.3

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @hapi/hoek. 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/hoek to 8.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-22h7-7wwg-qmgg 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-22h7-7wwg-qmgg 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-22h7-7wwg-qmgg. 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/hoek` prior to 8.5.1 and 9.0.3 are vulnerable to Prototype Pollution. The `clone` function fails to prevent the modification of the Object prototype when passed specially-crafted input. Attackers may use this to change existing properties that exist in all objects, which may lead to Denial of Service or Remote Code Execution in specific circumstances. This issue __does not__ affect hapi applications since the framework protects against such malicious inputs. Applications that use `@hapi/hoek` outside of the hapi ecosystem may be vulnerable. ## Recommendation Update to v

O3 Security · Impact-Aware SCA

Is GHSA-22h7-7wwg-qmgg in your dependencies?

O3 detects GHSA-22h7-7wwg-qmgg 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