Skip to content
Fencer Intel
low —

GHSA-jcgr-9698-82jx json

Improper Neutralization of Special Elements used in a Command ('Command Injection') in @floffah/build

published 5y ago modified 5y ago

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

Summary

### Impact If you are using the esbuild target or command you are at risk of code/option injection. Attackers can use the command line option to maliciously change your settings in order to damage your project.

### Patches The problem has been patched in v1.0.0 as it uses a proper method to pass configs to esbuild/estrella.

### Workarounds There is no work around. You should update asap.

### Notes This notice is mainly just to make sure people update to the latest version. This isn't that bad, but should encourage you to update.

Patch / fix

  • npm @floffah/build 1.0.0

Is GHSA-jcgr-9698-82jx 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 @floffah/build
<1.0.0
1.0.0

Classification

Weakness
  • CWE-77 Improper Neutralization of Special Elements used in a Command

References

Sources

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.