hull.js Code Injection Vulnerability

published 2024-12-02 last yr. modified 2024-12-02 last yr.

cvss: —; not scored
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

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

Patch / fix

fixed in 1 links 1

npm hull.js 1.0.10

github.com/AndriiHeonia/hull@9de6f95 commit

Is GHSA-q849-wxrc-vqrp in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem	package	affected	fixed in
npm	hull.js	>=0.2.2, <1.0.10	1.0.10

Classification

Weakness

CWE-94 Improper Control of Generation of Code

References

Sources

GitHub Advisory GHSA-q849-wxrc-vqrp

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.