NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

Unsanitized user controlled input in module generationGHSA-f8pq-3926-8gx5

HIGHFix: open-telemetry/opentelemetry-js@ffe641c

GHSA-f8pq-3926-8gx5 is a high-severity (CVSS 8.1) remote code execution vulnerability in @opentelemetry/instrumentation. A fix is available for @opentelemetry/instrumentation — see the affected versions and patch details below.

Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Aug 9, 2023 · 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.

1Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream
@opentelemetry/instrumentationnpm
145.1Mdownloads / week

Description

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

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npm@opentelemetry/instrumentation≥ 0.40.0&&< 0.41.20.41.2npm install @opentelemetry/instrumentation@0.41.2

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update @opentelemetry/instrumentation to 0.41.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f8pq-3926-8gx5 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 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 `@opent
O3 Security · Impact-Aware SCA

Is GHSA-f8pq-3926-8gx5 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Unsanitized user controlled input in module generation