How severe is GHSA-7x92-2j68-h32c?

No CVSS score has been assigned to GHSA-7x92-2j68-h32c yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-7x92-2j68-h32c?

GHSA-7x92-2j68-h32c affects the following packages: featurebook (npm). Ecosystems affected: npm.

How do I fix GHSA-7x92-2j68-h32c?

No patched version of featurebook has shipped for GHSA-7x92-2j68-h32c yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-7x92-2j68-h32c in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for featurebook. 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-7x92-2j68-h32c 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-7x92-2j68-h32c?

O3 pinpoints whether GHSA-7x92-2j68-h32c 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-7x92-2j68-h32c actively exploited in the wild?

No public exploit code has been indexed for GHSA-7x92-2j68-h32c 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-7x92-2j68-h32c published, and has it been updated?

GHSA-7x92-2j68-h32c was published on September 1, 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

Not in CISA KEV

GHSA-7x92-2j68-h32c

GHSA-7x92-2j68-h32c is a security vulnerability in featurebook. O3 Security confirms whether GHSA-7x92-2j68-h32c is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Directory Traversal in featurebook

Published

Sep 1, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · 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.

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

featurebooknpm

17downloads / week

Description

Affected versions of featurebook resolve relative file paths, resulting in a directory traversal vulnerability. A malicious actor can use this vulnerability to access files outside of the intended directory root, which may result in the disclosure of private files on the vulnerable system.

The featurebook package is not intended to be run in production code nor to be exposed to an untrusted network.

Proof of Concept

GET /../../../../../../../../../../etc/passwd HTTP/1.1
host:foo

Recommendation

No direct patch is currently available.

At this time, the best mitigation is to ensure that featurebook is not running in production or exposed to an untrusted network.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`featurebook`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for featurebook. 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.
Remediation status
No patched version of featurebook has shipped for GHSA-7x92-2j68-h32c yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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-7x92-2j68-h32c 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-7x92-2j68-h32c. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Affected versions of `featurebook` resolve relative file paths, resulting in a directory traversal vulnerability. A malicious actor can use this vulnerability to access files outside of the intended directory root, which may result in the disclosure of private files on the vulnerable system. The `featurebook` package is not intended to be run in production code nor to be exposed to an untrusted network. ## Proof of Concept ``` GET /../../../../../../../../../../etc/passwd HTTP/1.1 host:foo ``` ## Recommendation No direct patch is currently available. At this time, the best mitigation is

O3 Security · Impact-Aware SCA

Is GHSA-7x92-2j68-h32c in your dependencies?

O3 detects GHSA-7x92-2j68-h32c 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