LiveActive security incident?Get immediate response
CVE Record

CVE-2013-4238: The ssl.match_hostname function in the SSL module in Python 2.6 through 3.4 does not properly handle a '\0'...

The ssl.match_hostname function in the SSL module in Python 2.6 through 3.4 does not properly handle a '\0' character in a domain name in the Subject Alternative Name field of an X.509 certificate, which allows man-in-the-middle attackers to spoof arbitrary SSL servers via a crafted certificate issued by a legitimate Certification Authority, a related issue to CVE-2009-2408.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

Older Python SSL hostname checks could be fooled by a certificate containing a null character in a Subject Alternative Name. If an attacker could intercept traffic and had a crafted certificate issued by a trusted CA, they could impersonate SSL servers to affected Python clients. Exposure is most likely in legacy systems, appliances, or vendor products using affected Python 2.6 through 3.4 SSL hostname verification. The source bundle cites Linux distribution advisories and VMware vSphere updates, but does not provide a complete affected-product inventory. Prioritize remediation where legacy Python validates TLS for business-critical or credential-bearing connections. This is not listed as actively exploited in the supplied sources, but the potential impact is trust bypass and server impersonation. Mitigation focus: Apply relevant Python, OS, or vendor security updates from listed advisories.; Identify and retire unsupported Python 2.6 through 3.4 runtimes where possible.; Check VMware, Red Hat, Debian, Ubuntu, and openSUSE guidance for affected packages..

Prepared

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-2013-4238 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
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
2Source links

CVSS and timeline data

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

Source materials

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.