# CVE-2011-2201: Security feature bypass in n/a

> Remote attackers can bypass Perl's taint protection mechanism in Data::FormValidator when untaint_all_constraints is enabled, potentially leading to unsafe data handling.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Sep 2011
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2011-2201, GHSA-348p-57x3-vxc3

## What is CVE-2011-2201?

CVE-2011-2201 is a medium-severity vulnerability in n/a, published on 14 Sep 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Data::FormValidator module 4.66 and earlier for Perl, when untaint_all_constraints is enabled, does not properly preserve the taint attribute of data, which might allow remote attackers to bypass the taint protection mechanism via form input.

Weakness: CWE-264

## Which versions are affected by CVE-2011-2201?

It affects 1 product.


Products: Mark Stosberg Data\.

## How do I fix CVE-2011-2201?

Upgrade to a fixed version.

## Is CVE-2011-2201 being exploited?

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

Public exploit code:

- Perl Data::FormValidator 4.66 Module - 'results()' Security Bypass (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-2201 and fix it if it is affected.

What it is: CVE-2011-2201 is a medium-severity vulnerability in n/a, published on 14 Sep 2011. 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-2011-2201 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-2011-2201/ (Markdown: https://insights.sbomify.com/CVE-2011-2201/index.md)
```

## Sources

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

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