Description
libcloud before 0.4.1 does not verify SSL certificates for HTTPS connections, which allows remote attackers to spoof certificates and bypass intended access restrictions via a man-in-the-middle (MITM) attack.
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Debian
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian 14 | libcloud | 0.5.0-1 | — |
| Debian 13 | libcloud | 0.5.0-1 | — |
| Debian 12 | libcloud | 0.5.0-1 | — |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| PyPI | apache-libcloud | < 0.4.0 | 0.4.0 | GHSA-w3j6-8j34-q43x |
| PyPI | apache-libcloud | < 0.4.2 | 0.4.2 | PYSEC-2011-24 |
References
- [libcloud] 20100929 [jira] Closed: (LIBCLOUD-55) this python project is vulnerable to MITM as it fails to verify the ssl validity of the remote destination. mailing-list
- http://wiki.apache.org/incubator/LibcloudSSL
- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598463
- [libcloud] 20101108 SSL certs checking mailing-list
- https://issues.apache.org/jira/browse/LIBCLOUD-55