How severe is GHSA-3qh4-r86r-grvm?

No CVSS score has been assigned to GHSA-3qh4-r86r-grvm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3qh4-r86r-grvm?

GHSA-3qh4-r86r-grvm affects the following packages: typed-function (npm). Ecosystems affected: npm.

How do I fix GHSA-3qh4-r86r-grvm?

Update typed-function to 0.10.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3qh4-r86r-grvm is resolved across your whole dependency graph.

How do I detect GHSA-3qh4-r86r-grvm in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typed-function. 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-3qh4-r86r-grvm 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-3qh4-r86r-grvm?

O3 pinpoints whether GHSA-3qh4-r86r-grvm 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-3qh4-r86r-grvm actively exploited in the wild?

No public exploit code has been indexed for GHSA-3qh4-r86r-grvm 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-3qh4-r86r-grvm?

GHSA-3qh4-r86r-grvm is classified as Code Injection (CWE-94), Improper Input Validation (CWE-20). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-3qh4-r86r-grvm published, and has it been updated?

GHSA-3qh4-r86r-grvm was published on September 2, 2020 and was last updated on November 8, 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

GHSA-3qh4-r86r-grvm

Fix: josdejong/typed-function@6478ef4

GHSA-3qh4-r86r-grvm is a Code Injection vulnerability in typed-function. O3 Security confirms whether GHSA-3qh4-r86r-grvm is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Arbitrary JavaScript Execution in typed-function

Also known asCVE-2017-1001004

Published

Sep 2, 2020

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2023 · OSV.dev, NVD, 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.

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

typed-functionnpm

3.6Mdownloads / week

Description

Versions of typed-function prior to 0.10.6 are vulnerable to Arbitrary JavaScript Execution. Function names are not properly sanitized and may allow an attacker to execute arbitrary code.

Recommendation

Upgrade to version 0.10.6 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`typed-function`	all versions	0.10.6

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typed-function. 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 typed-function to 0.10.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3qh4-r86r-grvm 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-3qh4-r86r-grvm 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-3qh4-r86r-grvm. 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 `typed-function` prior to 0.10.6 are vulnerable to Arbitrary JavaScript Execution. Function names are not properly sanitized and may allow an attacker to execute arbitrary code. ## Recommendation Upgrade to version 0.10.6 or later.

O3 Security · Impact-Aware SCA

Is GHSA-3qh4-r86r-grvm in your dependencies?

O3 detects GHSA-3qh4-r86r-grvm 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