# CVE-2001-0113: Command injection in n/a

> Remote attackers can execute arbitrary commands on OmniHTTPd servers via the statsconfig.pl script's mostbrowsers parameter.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Feb 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-vcwg-qg38-hv98

## What is CVE-2001-0113?

CVE-2001-0113 is a critical command injection vulnerability in n/a, published on 14 Feb 2001. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

statsconfig.pl in OmniHTTPd 2.07 allows remote attackers to execute arbitrary commands via the mostbrowsers parameter, whose value is used as part of a generated Perl script.

## Which versions are affected by CVE-2001-0113?

It affects 1 product.


Products: Omnicron Omnihttpd.

## How do I fix CVE-2001-0113?

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

## Is CVE-2001-0113 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2001-0113 exists.

Public exploit code:

- Omnicron OmniHTTPd 2.0.7 - File Corruption / Command Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-1999-0951](https://insights.sbomify.com/CVE-1999-0951/): Memory corruption in n/a (critical 10.0)
- [CVE-2002-1035](https://insights.sbomify.com/CVE-2002-1035/): Denial of service in n/a (medium 5.0)
- [CVE-2001-0613](https://insights.sbomify.com/CVE-2001-0613/): Denial of service in n/a (medium 5.0)
- [CVE-2001-0777](https://insights.sbomify.com/CVE-2001-0777/): Denial of service in n/a (medium 5.0)
- [CVE-2001-0778](https://insights.sbomify.com/CVE-2001-0778/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-0113 and fix it if it is affected.

What it is: CVE-2001-0113 is a critical command injection vulnerability in n/a, published on 14 Feb 2001. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2001-0113 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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