CVE-2012-3446
published 2012-11-04CVE-2012-3446: Apache Libcloud before 0.11.1 uses an incorrect regular expression during verification of whether the server hostname matches a domain name in the subject's…
PriorityP424medium5.9CVSS 3.1
AVNACHPRNUINSUCNIHAN
EPSS
1.21%
64.8th percentile
Apache Libcloud before 0.11.1 uses an incorrect regular expression during verification of whether the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via a crafted certificate.
Affected
6 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| apache | libcloud | < 0.11.0 | 0.11.0 |
| apache | libcloud | >= 0 < 0.5.0-1.1 | 0.5.0-1.1 |
| apache | libcloud | >= 0 < 0.5.0-1.1 | 0.5.0-1.1 |
| apache | libcloud | >= 0 < 0.5.0-1.1 | 0.5.0-1.1 |
| apache | libcloud | >= 0 < 0.5.0-1.1 | 0.5.0-1.1 |
| debian | libcloud | < libcloud 0.5.0-1.1 (bookworm) | libcloud 0.5.0-1.1 (bookworm) |
CVSS provenance
nvdv3.15.9MEDIUMCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
nvdv2.05.8MEDIUMAV:N/AC:M/Au:N/C:P/I:P/A:N
osv5.9MEDIUM
vendor_debian5.9MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Debian
CVE-2012-3446: libcloud - Apache Libcloud before 0.11.1 uses an incorrect regular expression during verifi...
vendor_debian·2012·CVSS 5.9
CVE-2012-3446 [MEDIUM] CVE-2012-3446: libcloud - Apache Libcloud before 0.11.1 uses an incorrect regular expression during verifi...
Apache Libcloud before 0.11.1 uses an incorrect regular expression during verification of whether the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via a crafted certificate.
Scope: local
bookworm: resolved (fixed in 0.5.0-1.1)
bullseye: resolved (fixed in 0.5.0-1.1)
forky: resolved (fixed in 0.5.0-1.1)
sid: resolved (fixed in 0.5.0-1.1)
trixie: resolved (fixed in 0.5.0-1.1)
GHSA
Apache Libcloud vulnerable to certificate impersonation
ghsa·2022-05-17
CVE-2012-3446 [MEDIUM] CWE-185 Apache Libcloud vulnerable to certificate impersonation
Apache Libcloud vulnerable to certificate impersonation
Apache Libcloud before 0.11.1 uses an incorrect regular expression during verification of whether the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via a crafted certificate.
OSV
Apache Libcloud vulnerable to certificate impersonation
osv·2022-05-17
CVE-2012-3446 [MEDIUM] Apache Libcloud vulnerable to certificate impersonation
Apache Libcloud vulnerable to certificate impersonation
Apache Libcloud before 0.11.1 uses an incorrect regular expression during verification of whether the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via a crafted certificate.
OSV
CVE-2012-3446: Apache Libcloud before 0
osv·2012-11-04·CVSS 5.9
CVE-2012-3446 [MEDIUM] CVE-2012-3446: Apache Libcloud before 0
Apache Libcloud before 0.11.1 uses an incorrect regular expression during verification of whether the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via a crafted certificate.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2012-3446 libcloud: possible SSL MITM due to invalid regexp used to validate target server hostname
bugzilla·2012-08-03·CVSS 5.9
CVE-2012-3446 [MEDIUM] CVE-2012-3446 libcloud: possible SSL MITM due to invalid regexp used to validate target server hostname
CVE-2012-3446 libcloud: possible SSL MITM due to invalid regexp used to validate target server hostname
A man-in-the-middle vulnerability was reported [1] in Apache Libcloud, due to an invalid regular expression used to validate the target server hostname. When establishing an SSL/TLS connection to a target server, a subset of the full target server hostname was marked as an acceptable match for the given hostname (such as a certificate specifying "aexample.com" being considered acceptable for "example.com"). Upstream version 0.11.1 includes a fix for this flaw.
[1] http://seclists.org/fulldisclosure/2012/Aug/55
Discussion:
Created python-libcloud tracking bugs for this issue
Affects: fedora-all [bug 845666]
---
Current Fedora has 0.11.4 which includes this fix.
Bugzilla
CVE-2012-3446 libcloud: possible SSL MITM due to invalid regexp used to validate target server hostname [fedora-all]
bugzilla·2012-08-03·CVSS 5.9
CVE-2012-3446 [MEDIUM] CVE-2012-3446 libcloud: possible SSL MITM due to invalid regexp used to validate target server hostname [fedora-all]
CVE-2012-3446 libcloud: possible SSL MITM due to invalid regexp used to validate target server hostname [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected Fedora
versions.
For comments that are specific to the vulnerability please use bugs filed
against "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When creating a Bodhi update request, please include this bug ID and the
bug IDs of this bug's parent bugs filed against the "Security Response"
product (the top-level CVE bugs). Please mention the CVE IDs being fixed
in the RPM changelog when available.
Bodhi update submission link:
https://admin.fedo
CWE
Improper Validation of Certificate with Host Mismatch
mitre_cwe
CWE-297 Improper Validation of Certificate with Host Mismatch
CWE-297: Improper Validation of Certificate with Host Mismatch
The product communicates with a host that provides a certificate, but the product does not properly ensure that the certificate is actually associated with that host.
Even if a certificate is well-formed, signed, and follows the chain of trust, it may simply be a valid certificate for a different site than the site that the product is interacting with. If the certificate's host-specific data is not properly checked - such as the Common Name (CN) in the Subject or the Subject Alternative Name (SAN) extension of an X.509 certificate - it may be possible for a redirection or spoofing attack to allow a malicious host with a valid certificate to provide data, impersonating a trusted host. In order to ensure data integrity, the cer
CWE
Improper Certificate Validation
mitre_cwe
CWE-295 Improper Certificate Validation
CWE-295: Improper Certificate Validation
The product does not validate, or incorrectly validates, a certificate.
Background: A certificate is a token that associates an identity (principal) to a cryptographic key. Certificates can be used to check if a public key belongs to the assumed owner.
Modes of Introduction:
Phase: Architecture and Design
Phase: Implementation
Note: REALIZATION: This weakness is caused during implementation of an architectural security tactic.
Phase: Implementation
Note: When the product uses certificate pinning, the developer might not properly validate all relevant components of the certificate before pinning the certificate. This can make it difficult or expensive to test after the pinning is complete.
Common Consequences:
Scope: Integrity, Authentication. Im
2012-11-04
Published