Authenticated command execution via alert script filename
Published Jan 21, 2025 · Updated Feb 3, 2025
Command injection in Apache Ambari before 2.7.9 allows remote authenticated users to execute arbitrary shell commands through alert definitions. The Alert Definition script filename is inserted into a command executed by sh -c without neutralizing shell metacharacters, so crafted filenames become commands. Access to create or modify an alert definition is required, and successful exploitation runs commands with the Ambari server process's privileges.
Summary
What happened
Command injection in Apache Ambari before 2.7.9 allows remote authenticated users to execute arbitrary shell commands through alert definitions. The Alert Definition script filename is inserted into a command executed by sh -c without neutralizing shell metacharacters, so crafted filenames become commands. Access to create or modify an alert definition is required, and successful exploitation runs commands with the Ambari server process's privileges.
The record
- CVE
- CVE-2025-23196
- Published
- Jan 21, 2025
- Updated
- Feb 3, 2025
- Vendor
- The Apache Software Foundation
- Product
- Apache Ambari
- Classifications
- CWE-77, T1059.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 21, 2025CVE publishedPublication date reported by the CVE source.
- Feb 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=8 <2.7.9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo