# CVE-2010-2540: Security feature bypass in n/a

> Remote attackers can bypass security restrictions by exploiting improperly restricted debugging CGI arguments in MapServer.

- **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:** Yes
- **Published:** 2 Aug 2010
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-2540, GHSA-rvf8-gfc4-3j6f

## What is CVE-2010-2540?

CVE-2010-2540 is a critical vulnerability in n/a, published on 2 Aug 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

mapserv.c in mapserv in MapServer before 4.10.6 and 5.x before 5.6.4 does not properly restrict the use of CGI command-line arguments that were intended for debugging, which allows remote attackers to have an unspecified impact via crafted arguments.

Weakness: CWE-264

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

It affects 2 products.


Products: Osgeo Mapserver, Umn Mapserver.

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

Upgrade to a fixed version.

## Is CVE-2010-2540 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-2281](https://insights.sbomify.com/CVE-2009-2281/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-0839](https://insights.sbomify.com/CVE-2009-0839/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-0840](https://insights.sbomify.com/CVE-2009-0840/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-0841](https://insights.sbomify.com/CVE-2009-0841/): Path traversal in n/a (critical 10.0)
- [CVE-2009-1176](https://insights.sbomify.com/CVE-2009-1176/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-2540 is a critical vulnerability in n/a, published on 2 Aug 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-2540 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-2540/ (Markdown: https://insights.sbomify.com/CVE-2010-2540/index.md)
```

## Sources

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

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