Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm
Not in CISA KEV

Improper Neutralization of Special Elements used in a Command ('Command Injection') in @floffah/buildGHSA-jcgr-9698-82jx

GHSA-jcgr-9698-82jx is a security vulnerability in @floffah/build. A fix is available for @floffah/build — see the affected versions and patch details below.

Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of May 27, 2021 · 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
@floffah/buildnpm
10downloads / week

Description

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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npm@floffah/buildall versions1.0.0npm install @floffah/build@1.0.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update @floffah/build to 1.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jcgr-9698-82jx is resolved across your whole dependency graph.

  3. 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.

Frequently Asked Questions

### 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.
O3 Security · Impact-Aware SCA

Is GHSA-jcgr-9698-82jx in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Improper Neutralization of Special Elements used in a…