Filtered by vendor Cloudera
Subscriptions
Total
51 CVE
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2016-4950 | 1 Cloudera | 1 Manager | 2024-08-06 | N/A |
| Cloudera Manager 5.5 and earlier allows remote attackers to enumerate user sessions via a request to /api/v11/users/sessions. | ||||
| CVE-2016-4946 | 1 Cloudera | 1 Hue | 2024-08-06 | N/A |
| Multiple cross-site scripting (XSS) vulnerabilities in Cloudera HUE 3.9.0 and earlier allow remote attackers to inject arbitrary web script or HTML via the (1) First name or (2) Last name field in the HUE Users page. | ||||
| CVE-2016-4947 | 1 Cloudera | 1 Hue | 2024-08-06 | N/A |
| Cloudera HUE 3.9.0 and earlier allows remote attackers to enumerate user accounts via a request to desktop/api/users/autocomplete. | ||||
| CVE-2016-4572 | 1 Cloudera | 1 Cdh | 2024-08-06 | 8.8 High |
| In Cloudera CDH before 5.7.1, Impala REVOKE ALL ON SERVER commands do not revoke all privileges. | ||||
| CVE-2016-3192 | 1 Cloudera | 1 Cloudera Manager | 2024-08-05 | 6.5 Medium |
| Cloudera Manager 5.x before 5.7.1 places Sensitive Data in cleartext Readable Files. | ||||
| CVE-2016-3131 | 1 Cloudera | 1 Cdh | 2024-08-05 | 6.5 Medium |
| Cloudera CDH before 5.6.1 allows authorization bypass via direct internal API calls. | ||||
| CVE-2017-15536 | 1 Cloudera | 1 Data Science Workbench | 2024-08-05 | N/A |
| An issue was discovered in Cloudera Data Science Workbench (CDSW) 1.x before 1.2.0. Several web application vulnerabilities allow malicious authenticated users of CDSW to escalate privileges in CDSW. CDSW users can exploit these vulnerabilities in combination to gain root access to CDSW nodes, gain access to the CDSW database which includes Kerberos keytabs of CDSW users and bcrypt hashed passwords, and gain access to other privileged information such as session tokens, invitation tokens, and environment variables. | ||||
| CVE-2017-9325 | 1 Cloudera | 1 Cdh | 2024-08-05 | N/A |
| The provided secure solrconfig.xml sample configuration does not enforce Sentry authorization on /update/json/docs. | ||||
| CVE-2017-9327 | 1 Cloudera | 1 Cloudera Manager | 2024-08-05 | N/A |
| Secret data of processes managed by CM is not secured by file permissions. | ||||
| CVE-2017-9326 | 1 Cloudera | 1 Cloudera Manager | 2024-08-05 | N/A |
| The keystore password for the Spark History Server may be exposed in unsecured files under the /var/run/cloudera-scm-agent directory managed by Cloudera Manager. The keystore file itself is not exposed. | ||||
| CVE-2017-7399 | 1 Cloudera | 1 Cloudera Manager | 2024-08-05 | 8.8 High |
| Cloudera Manager 5.8.x before 5.8.5, 5.9.x before 5.9.2, and 5.10.x before 5.10.1 allows a read-only Cloudera Manager user to discover the usernames of other users and elevate the privileges of those users. | ||||
| CVE-2018-20091 | 1 Cloudera | 1 Data Science Workbench | 2024-08-05 | N/A |
| An SQL injection vulnerability was found in Cloudera Data Science Workbench (CDSW) 1.4.0 through 1.4.2. This would allow any authenticated user to run arbitrary queries against CDSW's internal database. The database contains user contact information, encrypted CDSW passwords (in the case of local authentication), API keys, and stored Kerberos keytabs. | ||||
| CVE-2018-20090 | 1 Cloudera | 1 Data Science Workbench | 2024-08-05 | 8.3 High |
| An issue was discovered in Cloudera Data Science Workbench (CDSW) 1.4.0 through 1.4.2. Authenticated users can bypass project permission checks and gain read-write access to any project folder. | ||||
| CVE-2018-17860 | 1 Cloudera | 1 Cdh | 2024-08-05 | 7.2 High |
| Cloudera CDH has Insecure Permissions because ALL cannot be revoked.This affects 5.x through 5.15.1 and 6.x through 6.0.1. | ||||
| CVE-2018-15913 | 1 Cloudera | 1 Cloudera Manager | 2024-08-05 | 6.1 Medium |
| An issue was discovered in Cloudera Manager 5.x through 5.15.0. One type of page in Cloudera Manager uses a 'returnUrl' parameter to redirect the user to another page in Cloudera Manager once a wizard is completed. The validity of this parameter was not checked. As a result, the user could be automatically redirected to an attacker's external site or perform a malicious JavaScript function that results in cross-site scripting (XSS). This was fixed by not allowing any value in the returnUrl parameter with patterns such as http://, https://, //, or javascript. The only exceptions to this rule are the SAML Login/Logout URLs, which remain supported since they are explicitly configured and they are not passed via the returnUrl parameter. | ||||
| CVE-2018-15665 | 1 Cloudera | 1 Data Science Workbench | 2024-08-05 | N/A |
| An issue was discovered in Cloudera Data Science Workbench (CDSW) 1.2.x through 1.4.0. Unauthenticated users can get a list of user accounts. | ||||
| CVE-2018-11744 | 1 Cloudera | 1 Cloudera Manager | 2024-08-05 | N/A |
| Cloudera Manager through 5.15 has Incorrect Access Control. | ||||
| CVE-2018-11215 | 1 Cloudera | 1 Data Science Workbench | 2024-08-05 | N/A |
| Remote code execution is possible in Cloudera Data Science Workbench version 1.3.0 and prior releases via unspecified attack vectors. | ||||
| CVE-2018-10815 | 1 Cloudera | 1 Cloudera Manager | 2024-08-05 | N/A |
| An issue was discovered in Cloudera Manager before 5.13.4, 5.14.x before 5.14.4, and 5.15.x before 5.15.1. A read-only user can access sensitive cluster information. | ||||
| CVE-2018-6185 | 1 Cloudera | 2 Cloudera Manager, Navigator Key Trustee Kms | 2024-08-05 | N/A |
| In Cloudera Navigator Key Trustee KMS 5.12 and 5.13, incorrect default ACL values allow remote access to purge and undelete API calls on encryption zone keys. The Navigator Key Trustee KMS includes 2 API calls in addition to those in Apache Hadoop KMS: purge and undelete. The KMS ACL values for these commands are keytrustee.kms.acl.PURGE and keytrustee.kms.acl.UNDELETE respectively. The default value for the ACLs in Key Trustee KMS 5.12.0 and 5.13.0 is "*" which allows anyone with knowledge of the name of an encryption zone key and network access to the Key Trustee KMS to make those calls against known encryption zone keys. This can result in the recovery of a previously deleted, but not purged, key (undelete) or the deletion of a key in active use (purge) resulting in loss of access to encrypted HDFS data. | ||||