# CVE-2010-4802: Other in n/a

> Improper CGI environment detection in Mojolicious Commands.pm allows remote attackers to exploit unspecified impacts.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 3 May 2011
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-4802, GHSA-9wxp-xqhf-2m53

## What is CVE-2010-4802?

CVE-2010-4802 is a critical vulnerability in n/a, published on 3 May 2011. It can be exploited over the network.

### Official description

Commands.pm in Mojolicious before 0.999928 does not properly perform CGI environment detection, which has unspecified impact and remote attack vectors.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2010-4802?

It affects 1 product.


Products: Mojolicious Mojolicious.

## How do I fix CVE-2010-4802?

Upgrade to a fixed version.

## Is CVE-2010-4802 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-5074](https://insights.sbomify.com/CVE-2009-5074/): Other in n/a (critical 10.0)
- [CVE-2010-4803](https://insights.sbomify.com/CVE-2010-4803/): Weak cryptography in n/a (critical 10.0)
- [CVE-2024-58134](https://insights.sbomify.com/CVE-2024-58134/): Hardcoded credentials in Mojolicious (high 8.1)
- [CVE-2024-58135](https://insights.sbomify.com/CVE-2024-58135/): Weak cryptography in Mojolicious (medium 5.3)
- [CVE-2011-1589](https://insights.sbomify.com/CVE-2011-1589/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-4802 and fix it if it is affected.

What it is: CVE-2010-4802 is a critical vulnerability in n/a, published on 3 May 2011. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2010-4802 in the wild and no public exploit code.

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

## Sources

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

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