CVE-2011-0633: n/a vulnerability

CVE-2011-0633: The Net::HTTPS module in libwww-perl (LWP) before 6.00, as used in WWW::Mechanize, LWP::UserAgent, and othe...

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.

UnknownCVSS not scoredNot KEV-listedUpdatedSep 16, 2024, 17:53 UTC (UTC+00:00)

Security readout for executives and security teams

Older Perl HTTP client libraries could accept an HTTPS connection without properly checking that the certificate belonged to the intended hostname. In affected applications, this could let a network-positioned attacker impersonate a trusted HTTPS service and read or alter traffic. Exposure is most likely in legacy Perl applications or scripts using libwww-perl before 6.00 for HTTPS requests, especially through LWP::UserAgent or WWW::Mechanize. The source bundle does not provide complete vendor/product inventory. Treat this as a legacy dependency risk rather than an emergency unless sensitive traffic still depends on affected Perl HTTPS clients. Prioritize systems handling credentials, tokens, payments, or administrative APIs. Mitigation focus: Upgrade libwww-perl to version 6.00 or later where feasible.; Inventory applications using LWP::UserAgent, WWW::Mechanize, or Net::HTTPS.; Confirm HTTPS clients perform full certificate and hostname validation..

Prepared: Jun 24, 2026, 13:28 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2011-0633 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: May 13, 2011, 22:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.