# CVE-2022-25760: Arbitrary Code Injection

> Attackers can execute arbitrary JavaScript code on the host by injecting malicious input into the format option of the accesslog package.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Mar 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-8m2f-74r2-x3f2

## What is CVE-2022-25760?

CVE-2022-25760 is a high-severity code injection vulnerability in accesslog, published on 17 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

All versions of package accesslog are vulnerable to Arbitrary Code Injection due to the usage of the Function constructor without input sanitization. If (attacker-controlled) user input is given to the format option of the package's exported constructor function, it is possible for an attacker to execute arbitrary JavaScript code on the host that this package is being run on.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2022-25760?

2 open source packages ship an affected version, including accesslog. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `accesslog` | npm | All versions to 0.0.2 | None |
| `accesslog` | npm | All versions to 0.0.2 | None |

Products: Accesslog Project Accesslog.

## How do I fix CVE-2022-25760?

No fix has been published for CVE-2022-25760 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-25760 being exploited?

There is no known exploitation of CVE-2022-25760 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-25760 and fix it if it is affected.

What it is: CVE-2022-25760 is a high-severity code injection vulnerability in accesslog, published on 17 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-25760 in the wild and no public exploit code.

Affected packages and fixed versions:
- accesslog (npm): affected all versions up to 0.0.2; no fix listed
- accesslog (npm): affected all versions up to 0.0.2; no fix listed

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/CVE-2022-25760/ (Markdown: https://insights.sbomify.com/CVE-2022-25760/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-25760
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-25760
- OSV: https://osv.dev/vulnerability/CVE-2022-25760

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-25760/
Summaries are generated and may contain mistakes; the official description above is the record.