Overview 26 matches · 10 in Waratek scope · 1 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
26matches
10in Waratek scope38.5%
1protected3.8%
0exploited0.0%
0CISA KEV0.0%
0public PoC0.0%
0EPSS ≥ 0.50.0%
Protected by Waratek
1
3.8%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
9
34.6%
Outside Waratek scope
0
0.0%
Not applicable
16
61.5%
Withdrawn CVE
0
0.0%
blocked by ARMR today
1
3.8%
partly blocked
0
0.0%
not blocked
25
96.2%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
26
100.0%
split by
peak 6 / year
20156
No exploit published2
Not applicable4
Medium4
Low2
not blocked6
No public exploit6
20162
Not applicable2
Medium1
Low1
not blocked2
No public exploit2
20176
No exploit published2
Not applicable4
Critical3
High1
Medium2
not blocked6
No public exploit6
20182
Not applicable2
High1
Medium1
not blocked2
No public exploit2
20190
20200
20212
No exploit published1
Not applicable1
High1
Medium1
not blocked2
No public exploit2
20220
20232
No exploit published2
High2
not blocked2
No public exploit2
20243
Protected by Waratek1
No exploit published2
High1
Medium2
blocked by ARMR today1
not blocked2
No public exploit3
20253
Not applicable3
High3
not blocked3
No public exploit3
20152016201720182019202020212022202320242025
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2025-23196 | High | 2025-01-21 | Not applicable | No public exploit | A code injection vulnerability exists in the Ambari Alert Definition feature, allowing authenticated users to inject and execute arbitrary shell commands. The vulnerability arises when defining alert scripts, where the script filename field is executed using `sh -c`. An attacker with authenticated access can exploit this vulnerability to inject malicious commands, leading to remote code execution on the server. The issue has been fixed in the latest versions of Ambari. |
| CVE-2025-23195 | High | 2025-01-21 | Not applicable | No public exploit | An XML External Entity (XXE) vulnerability exists in the Ambari/Oozie project, allowing an attacker to inject malicious XML entities. This vulnerability occurs due to insecure parsing of XML input using the `DocumentBuilderFactory` class without disabling external entity resolution. An attacker can exploit this vulnerability to read arbitrary files on the server or perform server-side request forgery (SSRF) attacks. The issue has been fixed in both Ambari 2.7.9 and the trunk branch. |
| CVE-2024-51941 | High | 2025-01-21 | Not applicable | No public exploit | A remote code injection vulnerability exists in the Ambari Metrics and AMS Alerts feature, allowing authenticated users to inject and execute arbitrary code. The vulnerability occurs when processing alert definitions, where malicious input can be injected into the alert script execution path. An attacker with authenticated access can exploit this vulnerability to execute arbitrary commands on the server. The issue has been fixed in the latest versions of Ambari. |
| CVE-2023-50378 | Medium | 2024-03-01 | No exploit published | No public exploit | Lack of proper input validation and constraint enforcement in Apache Ambari prior to 2.7.8 Impact : As it will be stored XSS, Could be exploited to perform unauthorized actions, varying from data access to session hijacking and delivering malicious payloads. Users are recommended to upgrade to version 2.7.8 which fixes this issue. |
| CVE-2023-50380 | Medium | 2024-02-27 | Protected by Waratek | No public exploit | XML External Entity injection in apache ambari versions <= 2.7.7, Users are recommended to upgrade to version 2.7.8, which fixes this issue. More Details: Oozie Workflow Scheduler had a vulnerability that allowed for root-level file reading and privilege escalation from low-privilege users. The vulnerability was caused through lack of proper user input validation. This vulnerability is known as an XML External Entity (XXE) injection attack. Attackers can exploit XXE vulnerabilities to read arbitrary files on the server, including sensitive system files. In theory, it might be possible to use this to escalate privileges. |
| CVE-2023-50379 | High | 2024-02-27 | No exploit published | No public exploit | Malicious code injection in Apache Ambari in prior to 2.7.8. Users are recommended to upgrade to version 2.7.8, which fixes this issue. Impact: A Cluster Operator can manipulate the request by adding a malicious code injection and gain a root over the cluster main host. |
| CVE-2022-45855 | High | 2023-07-12 | No exploit published | No public exploit | SpringEL injection in the metrics source in Apache Ambari version 2.7.0 to 2.7.6 allows a malicious authenticated user to execute arbitrary code remotely. Users are recommended to upgrade to 2.7.7. |
| CVE-2022-42009 | High | 2023-07-12 | No exploit published | No public exploit | SpringEL injection in the server agent in Apache Ambari version 2.7.0 to 2.7.6 allows a malicious authenticated user to execute arbitrary code remotely. Users are recommended to upgrade to 2.7.7. |
| CVE-2020-13924 | High | 2021-03-17 | Not applicable | No public exploit | In Apache Ambari versions 2.6.2.2 and earlier, malicious users can construct file names for directory traversal and traverse to other directories to download files. |
| CVE-2020-1936 | Medium | 2021-03-02 | No exploit published | No public exploit | A cross-site scripting issue was found in Apache Ambari Views. This was addressed in Apache Ambari 2.7.4. |
| CVE-2018-8042 | High | 2018-07-18 | Not applicable | No public exploit | Apache Ambari, version 2.5.0 to 2.6.2, passwords for Hadoop credential stores are exposed in Ambari Agent informational log messages when the credential store feature is enabled for eligible services. For example, Hive and Oozie. |
| CVE-2018-8003 | Medium | 2018-05-03 | Not applicable | No public exploit | Apache Ambari, versions 1.4.0 to 2.6.1, is susceptible to a directory traversal attack allowing an unauthenticated user to craft an HTTP request which provides read-only access to any file on the filesystem of the host the Ambari Server runs on that is accessible by the user the Ambari Server is running as. Direct network access to the Ambari Server is required to issue this request, and those Ambari Servers that are protected behind a firewall, or in a restricted network zone are at less risk of being affected by this issue. |
| CVE-2017-5655 | Medium | 2017-05-15 | Not applicable | No public exploit | In Ambari 2.2.2 through 2.4.2 and Ambari 2.5.0, sensitive data may be stored on disk in temporary files on the Ambari Server host. The temporary files are readable by any user authenticated on the host. |
| CVE-2017-5654 | High | 2017-05-12 | Not applicable | No public exploit | In Ambari 2.4.x (before 2.4.3) and Ambari 2.5.0, an authorized user of the Ambari Hive View may be able to gain unauthorized read access to files on the host where the Ambari server executes. |
| CVE-2017-5642 | Critical | 2017-04-03 | Not applicable | No public exploit | During installation of Ambari 2.4.0 through 2.4.2, Ambari Server artifacts are not created with proper ACLs. |
| CVE-2016-4976 | Medium | 2017-03-29 | No exploit published | No public exploit | Apache Ambari 2.x before 2.4.0 includes KDC administrator passwords on the kadmin command line, which allows local users to obtain sensitive information via a process listing. |
| CVE-2014-3582 | Critical | 2017-03-29 | Not applicable | No public exploit | In Ambari 1.2.0 through 2.2.2, it may be possible to execute arbitrary system commands on the Ambari Server host while generating SSL certificates for hosts in an Ambari cluster. |
| CVE-2016-6807 | Critical | 2017-03-28 | No exploit published | No public exploit | Custom commands may be executed on Ambari Agent (2.4.x, before 2.4.2) hosts without authorization, leading to unauthorized access to operations that may affect the underlying system. Such operations are invoked by the Ambari Agent process on Ambari Agent hosts, as the user executing the Ambari Agent process. |
| CVE-2016-0731 | Medium | 2016-05-18 | Not applicable | No public exploit | The File Browser View in Apache Ambari before 2.2.1 allows remote authenticated administrators to read arbitrary files via a file: URL in the WebHDFS URL configuration. |
| CVE-2016-0707 | Low | 2016-05-18 | Not applicable | No public exploit | The agent in Apache Ambari before 2.1.2 uses weak permissions for the (1) /var/lib/ambari-agent/data and (2) /var/lib/ambari-agent/keys directories, which allows local users to obtain sensitive information by reading files in the directories. |
| CVE-2015-4940 | Low | 2015-11-08 | Not applicable | No public exploit | Apache Ambari before 2.1, as used in IBM Infosphere BigInsights 4.x before 4.1, stores a cleartext BigSheets password in a configuration file, which allows local users to obtain sensitive information by reading this file. |
| CVE-2015-4928 | Medium | 2015-11-08 | Not applicable | No public exploit | Apache Ambari before 2.1, as used in IBM Infosphere BigInsights 4.x before 4.1, includes cleartext passwords on a Configs screen, which allows physically proximate attackers to obtain sensitive information by reading password fields. |
| CVE-2015-5210 | Medium | 2015-11-02 | No exploit published | No public exploit | Open redirect vulnerability in Apache Ambari before 2.1.2 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL in the targetURI parameter. |
| CVE-2015-3270 | Medium | 2015-11-02 | Not applicable | No public exploit | Apache Ambari before 2.0.2 or 2.1.x before 2.1.1 allows remote authenticated users to gain administrative privileges via unspecified vectors, possibly related to changing passwords. |
| CVE-2015-3186 | Low | 2015-11-02 | Not applicable | No public exploit | Cross-site scripting (XSS) vulnerability in Apache Ambari before 2.1.0 allows remote authenticated cluster operator users to inject arbitrary web script or HTML via the note field in a configuration change. |
| CVE-2015-1775 | Medium | 2015-11-02 | No exploit published | No public exploit | Server-side request forgery (SSRF) vulnerability in the proxy endpoint (api/v1/proxy) in Apache Ambari before 2.1.0 allows remote authenticated users to conduct port scans and access unsecured services via a crafted REST call. |