How severe is GHSA-q849-wxrc-vqrp?

No CVSS score has been assigned to GHSA-q849-wxrc-vqrp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-q849-wxrc-vqrp?

GHSA-q849-wxrc-vqrp affects the following packages: hull.js (npm). Ecosystems affected: npm.

How do I fix GHSA-q849-wxrc-vqrp?

Update hull.js to 1.0.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q849-wxrc-vqrp is resolved across your whole dependency graph.

How do I detect GHSA-q849-wxrc-vqrp in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hull.js, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-q849-wxrc-vqrp 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-q849-wxrc-vqrp?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-q849-wxrc-vqrp can be triaged on real exposure rather than presence alone.

Is GHSA-q849-wxrc-vqrp actively exploited in the wild?

No public exploit code has been indexed for GHSA-q849-wxrc-vqrp 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-q849-wxrc-vqrp published, and has it been updated?

GHSA-q849-wxrc-vqrp was published on December 2, 2024. 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-q849-wxrc-vqrp — hull.js

Fix: AndriiHeonia/hull@9de6f95

GHSA-q849-wxrc-vqrp is a remote code execution vulnerability in hull.js. A fix is available for hull.js — see the affected versions and patch details below.

hull.js Code Injection Vulnerability

Published

Dec 2, 2024

Updated

Dec 2, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 2, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

hull.jsnpm

12Kdownloads / week

Description

Versions of the library from 0.2.2 to 1.0.9 are vulnerable to the arbitrary code execution due to unsafe usage of new Function(...) in the module that handles points format. Applications passing the 3rd parameter to the hull function without sanitising may be impacted. The vulnerability has been fixed in version 1.0.10, please update the library. Check project homepage on GitHub to see how to fetch the latest version: https://github.com/andriiheonia/hull?tab=readme-ov-file#npm-package

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`hull.js`	≥ 0.2.2&&< 1.0.10	1.0.10`npm install hull.js@1.0.10`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hull.js, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update hull.js to 1.0.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q849-wxrc-vqrp 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-q849-wxrc-vqrp can be triaged on real exposure rather than presence alone.

Tailored to GHSA-q849-wxrc-vqrp. 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 the library from 0.2.2 to 1.0.9 are vulnerable to the arbitrary code execution due to unsafe usage of `new Function(...)` in the module that handles points format. Applications passing the 3rd parameter to the `hull` function without sanitising may be impacted. The vulnerability has been fixed in version 1.0.10, please update the library. Check project homepage on GitHub to see how to fetch the latest version: https://github.com/andriiheonia/hull?tab=readme-ov-file#npm-package

O3 Security · Impact-Aware SCA

Is GHSA-q849-wxrc-vqrp in your dependencies?

O3 Security finds GHSA-q849-wxrc-vqrp across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works