| --- |
| layout: page_with_sidebar |
| title: Security |
| description: See a list of known vulnerabilities which have been fixed and find information on how to report a new vulnerability |
| --- |
| |
| # {{ page.title }} |
| |
| ## Security Vulnerabilities |
| |
| ### [CVE-2013-6480] Libcloud doesn't send scrub\_data query parameter when destroying a DigitalOcean node |
| |
| **Severity**: Low |
| **Affected Versions**: Apache Libcloud **0.12.3** to **0.13.3** (version prior |
| to 0.12.3 don't include a DigitalOcean driver) |
| **Description**: |
| |
| DigitalOcean recently changed the default API behavior from scrub to non-scrub |
| when destroying a VM. |
| |
| Libcloud doesn't explicitly send "scrub_data" query parameter when destroying a |
| node. This means nodes which are destroyed using Libcloud are vulnerable to |
| later customers stealing data contained on them. |
| |
| Note: Only users who are using DigitalOcean driver are affected by this issue. |
| |
| References: |
| |
| * <a href="https://digitalocean.com/blog_posts/transparency-regarding-data-security" rel="nofollow">https://digitalocean.com/blog_posts/transparency-regarding-data-security</a> |
| * <a href="https://github.com/fog/fog/issues/2525" rel="nofollow">https://github.com/fog/fog/issues/2525</a> |
| |
| **Mitigation**: |
| |
| This vulnerability has been fixed in version 0.13.3. Users who use DigitalOcean |
| driver are strongly encouraged to upgrade to this release. |
| |
| ### [CVE-2012-3446] Possible SSL MITM due to invalid regular expression used to validate the target server hostname |
| |
| **Severity**: Medium |
| **Affected Versions**: Apache Libcloud 0.4.2 to 0.11.1 (version prior to 0.4.2 |
| don't preform any target SSL certificate validation) |
| **Description**: |
| |
| When establishing a secure (SSL / TLS) connection to a target server an |
| invalid regular expression has been used for performing the hostname |
| verification. Subset instead of the full target server hostname has been |
| marked as an acceptable match for the given hostname. |
| |
| For example, certificate with a hostname field of `aexample.com` was considered |
| a valid certificate for domain `example.com`. |
| |
| **Mitigation**: |
| |
| This vulnerability has been fixed in version 0.11.1 so all the users should |
| upgrade to version 0.11.1 or higher. |
| |
| **Credits**: |
| |
| This issue was discovered by researchers from the University of Texas at Austin |
| (Martin Georgiev, Suman Jana and Vitaly Shmatikov). |
| |
| ### [CVE-2010-4340] SSL MITM vulnerability |
| |
| **Severity**: Medium |
| **Affected versions**: All the versions prior to **0.4.2** |
| **Description**: |
| |
| Python SSL library doesn't validate a host SSL certificate and as a |
| consequence, versions prior to **0.4.2** are vulnerable to a man-in-the-middle |
| attack. |
| |
| **Mitigation**: |
| |
| This vulnerability has been fixed in the version 0.4.2. You are strongly |
| encouraged to upgrade to this version and set |
| `libcloud.security.VERIFY_SSL_CERT` variable to `True`. |
| |
| ## Reporting a Vulnerability |
| |
| _Please do <strong>not</strong> report security issues using our public Github instance. Use the private mailing list described bellow._ |
| |
| If you believe you found a security issue or a vulnerability, please send a |
| description of it to our private mailing list at |
| [security@libcloud.apache.org][3]. |
| |
| You are also encouraged to encrypt this email using PGP. Keys of our developers |
| can be found at [https://www.apache.org/dist/libcloud/KEYS][4]. |
| |
| Once you've submitted an issue, you should receive an acknowledgment from one |
| our of team members in 48 hours or less. If further action is necessary, you |
| may receive additional follow-up emails. |
| |
| ## How are vulnerabilities handled? |
| |
| We follow a standard Apache Software Foundation vulnerability handling process |
| which is described at |
| [http://www.apache.org/security/committers.html#vulnerability-handling][5]. |
| |
| ## Errors and Omissions |
| |
| Please report any errors or omissions to |
| <a href="mailto:security@libcloud.apache.org">security@libcloud.apache.org</a>. |
| |
| [1]: {{ page.url }} |
| [2]: https://libcloud.readthedocs.org/en/stable/security.html#reporting-a-vulnerability |
| [3]: mailto:security@libcloud.apache.org |
| [4]: https://www.apache.org/dist/libcloud/KEYS |
| [5]: http://www.apache.org/security/committers.html#vulnerability-handling |