Total
22 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2016-8520 | 1 Eucalyptus | 1 Eucalyptus | 2023-12-10 | 6.5 MEDIUM | 8.8 HIGH |
| HPE Helion Eucalyptus v4.3.0 and earlier does not correctly check IAM user's permissions for accessing versioned objects and ACLs. In some cases, authenticated users with S3 permissions could also access versioned data. | |||||
| CVE-2016-8528 | 1 Eucalyptus | 1 Eucalyptus | 2023-12-10 | 6.5 MEDIUM | 8.8 HIGH |
| A Remote Escalation of Privilege vulnerability in HPE Helion Eucalyptus version 3.3.0 through 4.3.1 was found. | |||||
| CVE-2017-7999 | 1 Eucalyptus | 1 Eucalyptus | 2023-12-10 | 3.5 LOW | 6.5 MEDIUM |
| Atlassian Eucalyptus before 4.4.1, when in EDGE mode, allows remote authenticated users with certain privileges to cause a denial of service (E2 service outage) via unspecified vectors. | |||||
| CVE-2015-6861 | 1 Eucalyptus | 1 Eucalyptus | 2023-12-10 | 4.6 MEDIUM | 7.5 HIGH |
| HPE Helion Eucalyptus 3.4.0 through 4.2.0 allows remote authenticated users to bypass an intended AssumeRole permission requirement and assume an IAM role by leveraging a policy setting for a user's account. | |||||
| CVE-2014-5040 | 1 Eucalyptus | 1 Eucalyptus | 2023-12-10 | 4.6 MEDIUM | 6.8 MEDIUM |
| HP Helion Eucalyptus 4.1.x before 4.1.2 and HPE Helion Eucalyptus 4.2.x before 4.2.1 allow remote authenticated users to bypass intended access restrictions and modify arbitrary (1) access key credentials by leveraging knowledge of a key ID or (2) signing certificates by leveraging knowledge of a certificate ID. | |||||
| CVE-2013-4769 | 1 Eucalyptus | 1 Eucalyptus | 2023-12-10 | 4.3 MEDIUM | N/A |
| The cloud controller (aka CLC) component in Eucalyptus 3.3.x and 3.4.x before 3.4.2, when the dns.recursive.enabled setting is used, allows remote attackers to cause a denial of service (traffic amplification) via spoofed DNS queries. | |||||
| CVE-2013-4768 | 1 Eucalyptus | 1 Eucalyptus | 2023-12-10 | 5.0 MEDIUM | N/A |
| The web services APIs in Eucalyptus 2.0 through 3.4.1 allow remote attackers to cause a denial of service via vectors related to the "network connection clean up code" and (1) Cloud Controller (CLC), (2) Walrus, (3) Storage Controller (SC), and (4) VMware Broker (VB). | |||||
| CVE-2014-5038 | 1 Eucalyptus | 1 Eucalyptus | 2023-12-10 | 2.1 LOW | N/A |
| Eucalyptus 3.0.0 through 4.0.1, when the log level is set to DEBUG or lower, logs user and system passwords, which allows local users to obtain sensitive information by reading the cloud log files. | |||||
| CVE-2014-5036 | 1 Eucalyptus | 1 Eucalyptus | 2023-12-10 | 1.9 LOW | N/A |
| The Storage Controller (SC) component in Eucalyptus 3.4.2 through 4.0.x before 4.0.1, when Dell Equallogic SAN is used, logs the CHAP user credentials, which allows local users to obtain sensitive information by reading the logs. | |||||
| CVE-2014-5037 | 1 Eucalyptus | 1 Eucalyptus | 2023-12-10 | 2.1 LOW | N/A |
| Eucalyptus 4.0.0 through 4.0.1, when the log level is set to INFO, logs user and system passwords, which allows local users to obtain sensitive information by reading cloud-requests.log. | |||||
| CVE-2012-4067 | 1 Eucalyptus | 1 Eucalyptus | 2023-12-10 | 4.3 MEDIUM | N/A |
| Walrus in Eucalyptus before 3.2.2 allows remote attackers to cause a denial of service (memory, thread, and CPU consumption) via a crafted XML message containing a DTD, as demonstrated by a bucket-logging request. | |||||
| CVE-2012-4063 | 1 Eucalyptus | 1 Eucalyptus | 2023-12-10 | 5.0 MEDIUM | N/A |
| The Apache Santuario configuration in Eucalyptus before 3.1.1 does not properly restrict applying XML Signature transforms to documents, which allows remote attackers to cause a denial of service via unspecified vectors. | |||||
| CVE-2013-4766 | 1 Eucalyptus | 1 Eucalyptus | 2023-12-10 | 4.3 MEDIUM | N/A |
| The gather log service in Eucalyptus before 3.3.1 allows remote attackers to read log files via an unspecified request to the (1) Cluster Controller (CC) or (2) Node Controller (NC) component. | |||||
| CVE-2013-4767 | 1 Eucalyptus | 1 Eucalyptus | 2023-12-10 | 10.0 HIGH | N/A |
| Unspecified vulnerability in Eucalyptus before 3.3.2 has unknown impact and attack vectors. | |||||
| CVE-2012-3241 | 1 Eucalyptus | 1 Eucalyptus | 2023-12-10 | 7.5 HIGH | N/A |
| The VMware Broker in Eucalyptus 2.0.3 and 3.0.x before 3.0.2 does not properly authenticate SOAP requests, which allows remote attackers to execute arbitrary VMware Broker API commands. | |||||
| CVE-2012-4065 | 1 Eucalyptus | 1 Eucalyptus | 2023-12-10 | 3.5 LOW | N/A |
| Eucalyptus before 3.1.1 does not properly restrict the binding of external SOAP web-services messages, which allows remote authenticated users to bypass unspecified authorization checks and obtain direct access to a (1) Cloud Controller or (2) Walrus service via a crafted message, as demonstrated by changes to a volume, snapshot, or cloud configuration setting. | |||||
| CVE-2012-4064 | 1 Eucalyptus | 1 Eucalyptus | 2023-12-10 | 6.5 MEDIUM | N/A |
| Eucalyptus before 3.1.1 does not properly restrict the binding of external SOAP web-services messages, which allows remote authenticated users to gain privileges by sending a message to (1) Cloud Controller or (2) Walrus with the internal message format and a modified user id. | |||||
| CVE-2012-3240 | 1 Eucalyptus | 1 Eucalyptus | 2023-12-10 | 7.5 HIGH | N/A |
| The Walrus service in Eucalyptus 2.0.3 and 3.0.x before 3.0.2 allows remote attackers to gain administrator privileges via a crafted REST request. | |||||
| CVE-2012-4066 | 1 Eucalyptus | 1 Eucalyptus | 2023-12-10 | 5.0 MEDIUM | N/A |
| The internal message protocol for Walrus in Eucalyptus 3.2.0 and earlier does not require signatures for unspecified request headers, which allows attackers to (1) delete or (2) upload snapshots. | |||||
| CVE-2013-2296 | 1 Eucalyptus | 1 Eucalyptus | 2023-12-10 | 5.5 MEDIUM | N/A |
| Walrus in Eucalyptus before 3.2.2 does not verify authorization for the GetBucketLoggingStatus, SetBucketLoggingStatus, and SetBucketVersioningStatus bucket operations, which allows remote authenticated users to bypass intended restrictions on (1) modifying the logging setting, (2) modifying the versioning setting, or (3) accessing activity logs via a request. | |||||