Packages / @opentelemetry/instrumentation / Security

HighVulnerabilityGHSA-f8pq-3926-8gx5Published 9 Aug 2023

Unsanitized user controlled input in module generation

Your version

Affected releases · @opentelemetry/instrumentation

  • 0.41.x0.41.0 – 0.41.1Fixed in 0.41.2
  • 0.40.x0.40.0No fix on this line yet

On 0.41.x, the newest line:

npm install @opentelemetry/instrumentation@0.41.2
Every release on a timeline

  1. Not affected

    0.12.0 – 0.39.1

    35 releases

  2. Affected

    0.40.0 – 0.41.1

    3 releases

  3. Fixed

    0.41.2 – 0.300.0

    51 releases, latest

89 stable releases of @opentelemetry/instrumentation, oldest to newest.

What happens

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