# GHSA-f8pq-3926-8gx5: Unsanitized user controlled input in module generation

> Attackers can execute arbitrary code if user input is passed to import() when using the OpenTelemetry instrumentation loader.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Aug 2023

## What is GHSA-f8pq-3926-8gx5?

GHSA-f8pq-3926-8gx5 is a code injection vulnerability in @opentelemetry/instrumentation, published on 9 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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

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

## Which versions are affected by GHSA-f8pq-3926-8gx5?

2 open source packages ship an affected version, including @opentelemetry/instrumentation.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@opentelemetry/instrumentation` | npm | From 0.40.0 | 0.41.2 |
| `@opentelemetry/instrumentation` | npm | From 0.40.0 | 0.41.2 |

## How do I fix GHSA-f8pq-3926-8gx5?

Upgrade @opentelemetry/instrumentation to 0.41.2 or later.

## Is GHSA-f8pq-3926-8gx5 being exploited?

There is no known exploitation of GHSA-f8pq-3926-8gx5 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-f8pq-3926-8gx5 and fix it if it is affected.

What it is: GHSA-f8pq-3926-8gx5 is a code injection vulnerability in @opentelemetry/instrumentation, published on 9 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-f8pq-3926-8gx5 in the wild and no public exploit code.

Affected packages and fixed versions:
- @opentelemetry/instrumentation (npm): affected from 0.40.0; fixed in 0.41.2
- @opentelemetry/instrumentation (npm): affected from 0.40.0; fixed in 0.41.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-f8pq-3926-8gx5/ (Markdown: https://insights.sbomify.com/GHSA-f8pq-3926-8gx5/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-f8pq-3926-8gx5

---
From sbomify Insights: https://insights.sbomify.com/GHSA-f8pq-3926-8gx5/
Summaries are generated and may contain mistakes; the official description above is the record.