apache-libcloud vulnerabilities — 6 matching vulnerabilities
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed — no installation and no source-code access required.
| Severity | Vulnerability | Package | Ecosystem | Disclosed | Fixed version |
|---|---|---|---|---|---|
| 7.5 high | CVE-2010-4340: Apache Libcloud SSL Certificate Verification Bypass |
apache-libcloud
|
PyPI | 17 May 2022 | 0.4.0 |
| 5.9 medium | Apache Libcloud Vulnerable to Certificate Impersonation |
apache-libcloud
|
PyPI | 17 May 2022 | 0.11.1 |
| Low | CVE-2013-6480: Vulnerability in apache-libcloud - Improper Data Scrubbing |
apache-libcloud
|
PyPI | 14 May 2022 | 0.13.3 |
| Unrated | CVE-2013-6480: Vulnerability in apache-libcloud |
apache-libcloud
|
PyPI | 07 Jan 2014 | 0.13.3 |
| Unrated | CVE-2012-3446: Apache Libcloud SSL Server Spoofing |
apache-libcloud
|
PyPI | 04 Nov 2012 | 0.11.1 |
| Unrated | CVE-2010-4340: SSL Certificate Verification Bypass in apache-libcloud |
apache-libcloud
|
PyPI | 12 Sep 2011 | 0.4.2 |
Questions
Searching the database
How do I search for a CVE or a package?
Type a CVE id, package name, ecosystem or keyword into the search field. Results include the severity, the affected package, the ecosystem, the disclosure date and the fixed version.
Can I filter by severity or by whether a fix exists?
Yes. The filters on the left narrow the list to critical, high, medium or low vulnerabilities, to a single ecosystem, and to vulnerabilities that have a fix available or none yet.
What does "No fix published" mean?
No patched version has been released for that vulnerability yet. The vulnerability page still shows the affected range and any workaround that can reduce exposure in the meantime.