Skip to content
Fencer Intel
high 8.1

GHSA-f8pq-3926-8gx5 json

Unsanitized user controlled input in module generation

published 3y ago modified 3y ago

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

Summary

## Impact

The `import-in-the-middle` loader used by `@opentelemetry/instrumentation` works by generating a wrapper module on the fly. The wrapper uses the module specifier to load the original module and add some wrapping code. It allows for remote code execution in cases where an application passes user-supplied input directly to an `import()` function.

## Patches

This vulnerability has been patched in `@opentelemetry/instrumentation` version `0.41.2`

## Workarounds

- Do not pass any user-supplied input to `import()`. Instead, verify it against a set of allowed values. - If using `@opentelemetry/instrumentation` with support for EcmaScript Modules is not needed, ensure that none of the following options are set (either via command-line or the `NODE_OPTIONS` environment variable): ``` --experimental-loader=@opentelemetry/instrumentation/hook.mjs --experimental-loader @opentelemetry/instrumentation/hook.mjs --loader=import-in-the-middle/hook.mjs --loader import-in-the-middle/hook.mjs ```

## References

- https://github.com/DataDog/import-in-the-middle/security/advisories/GHSA-5r27-rw8r-7967

Patch / fix

  • npm @opentelemetry/instrumentation 0.41.2

Is GHSA-f8pq-3926-8gx5 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

CVSS scores

assigned by version score vector
GitHub 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:L

Affected packages

ecosystem package affected fixed in
npm @opentelemetry/instrumentation
>=0.40.0, <0.41.2
0.41.2

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.

The maintainers of open-telemetry/opentelemetry-js published their own advisory on GitHub. Reviewed sources take precedence over it.