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

> Remote attackers can spoof servers via man-in-the-middle attacks because the library does not validate SSL certificates by default.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/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:** 13 May 2011
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2011-0633, GHSA-3fhh-g5rg-6jpm

## What is CVE-2011-0633?

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

### Official description

The Net::HTTPS module in libwww-perl (LWP) before 6.00, as used in WWW::Mechanize, LWP::UserAgent, and other products, when running in environments that do not set the If-SSL-Cert-Subject header, does not enable full validation of SSL certificates by default, which allows remote attackers to spoof servers via man-in-the-middle (MITM) attacks involving hostnames that are not properly validated.  NOTE: it could be argued that this is a design limitation of the Net::HTTPS API, and separate implementations should be independently assigned CVE identifiers for not working around this limitation. However, because this API was modified within LWP, a single CVE identifier has been assigned.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: Gisle Aas Libwww-Perl, Search.cpan Libwww-Perl.

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

Upgrade to a fixed version.

## Is CVE-2011-0633 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-2253](https://insights.sbomify.com/CVE-2010-2253/): Path traversal in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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