Skip to content
Noroxi
CVE-2011-0633· NVD / CVE Program· CNA mitre

The Net::HTTPS module in libwww-perl (LWP) before 6.00, as used in WWW::Mechanize, LWP::UserAgent, and other products, when running in envir

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.

MediumCVSS 4.3 · v2.0—No exploit Fix available
Published
May 13, 2011
Updated
Jun 16, 2026
EPSS
4.2% · 91th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
17 / 40 · 4.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 4.2%

Affected systems

VendorProduct
gisle aaslibwww-perl
search.cpanlibwww-perl

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • gisle aas libwww-perl0.01
  • gisle aas libwww-perl0.02
  • gisle aas libwww-perl0.03
  • gisle aas libwww-perl0.04
  • gisle aas libwww-perl5.00
  • gisle aas libwww-perl5.01
  • gisle aas libwww-perl5.02
  • gisle aas libwww-perl5.03
  • gisle aas libwww-perl5.04
  • gisle aas libwww-perl5.05
  • gisle aas libwww-perl5.06
  • gisle aas libwww-perl5.07
  • gisle aas libwww-perl5.08
  • gisle aas libwww-perl5.09
  • gisle aas libwww-perl5.10
  • gisle aas libwww-perl5.11
  • gisle aas libwww-perl5.12
  • gisle aas libwww-perl5.13
  • gisle aas libwww-perl5.14
  • gisle aas libwww-perl5.15

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12libwww-perlbefore 6.01-16.01-1

Other highest-scoring records for the same primary product.

  • CVE-2010-2253lwp-download in libwww-perl before 5.835 does not reject downloads to filenames that begin with a .
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:libwww-perl6.01-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records