[
https://issues.apache.org/jira/browse/AMBARI-26306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Basapuram Kumar updated AMBARI-26306:
-------------------------------------
Description:
Currenlty Ambari is using 1.2.13 version of logback-classic & logback-core,
which is the vulnerable to following CVE's
{{[CVE-2024-12801|https://nvd.nist.gov/vuln/detail/CVE-2024-12801] }}
{{[CVE-2024-12798|https://nvd.nist.gov/vuln/detail/CVE-2024-12798] }}
{{Description of the above CVE;s}}
{{```}}
ACE vulnerability in JaninoEventEvaluator by QOS.CH logback-core upto including
version 0.1 to 1.3.14 and 1.4.0 to 1.5.12 in Java applications allows attacker
to execute arbitrary code by compromising an existing logback configuration
file or by injecting an environment variable before program execution.
Malicious logback configuration files can allow the attacker to execute
arbitrary code using the JaninoEventEvaluator extension. A successful attack
requires the user to have write access to a configuration file. Alternatively,
the attacker could inject a malicious environment variable pointing to a
malicious configuration file. In both cases, the attack requires existing
privilege.
```
{{So suggesting to upgrade to latest version, which is 1.5.16, which is
compiled in jdk-11, should be able to compatible.}}
was:
Currenlty Ambari is using 1.2.13 version of logback-classic & logback-core,
which is the vulnerable to following CVE's
{{[CVE-2024-12801|https://nvd.nist.gov/vuln/detail/CVE-2024-12801] }}
{{[CVE-2024-12798|https://nvd.nist.gov/vuln/detail/CVE-2024-12798] }}
{{Description of the above CVE;s}}
{{```}}
ACE vulnerability in JaninoEventEvaluator by QOS.CH logback-core upto including
version 0.1 to 1.3.14 and 1.4.0 to 1.5.12 in Java applications allows attacker
to execute arbitrary code by compromising an existing logback configuration
file or by injecting an environment variable before program execution.
Malicious logback configuration files can allow the attacker to execute
arbitrary code using the JaninoEventEvaluator extension. A successful attack
requires the user to have write access to a configuration file. Alternatively,
the attacker could inject a malicious environment variable pointing to a
malicious configuration file. In both cases, the attack requires existing
privilege.
```
{{}}
{{So suggesting to upgrade tot he latest version, whcih is 1.5.16, which is
compiled in jdk-11, should be able to compatible.}}
{{}}
> Bumpup logback to 1.5.16(latest) due to CVE's
> ---------------------------------------------
>
> Key: AMBARI-26306
> URL: https://issues.apache.org/jira/browse/AMBARI-26306
> Project: Ambari
> Issue Type: Improvement
> Reporter: Basapuram Kumar
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currenlty Ambari is using 1.2.13 version of logback-classic & logback-core,
> which is the vulnerable to following CVE's
>
> {{[CVE-2024-12801|https://nvd.nist.gov/vuln/detail/CVE-2024-12801] }}
> {{[CVE-2024-12798|https://nvd.nist.gov/vuln/detail/CVE-2024-12798] }}
> {{Description of the above CVE;s}}
> {{```}}
> ACE vulnerability in JaninoEventEvaluator by QOS.CH logback-core upto
> including version 0.1 to 1.3.14 and 1.4.0 to 1.5.12 in Java applications
> allows attacker to execute arbitrary code by compromising an existing logback
> configuration file or by injecting an environment variable before program
> execution. Malicious logback configuration files can allow the attacker to
> execute arbitrary code using the JaninoEventEvaluator extension. A successful
> attack requires the user to have write access to a configuration file.
> Alternatively, the attacker could inject a malicious environment variable
> pointing to a malicious configuration file. In both cases, the attack
> requires existing privilege.
> ```
>
> {{So suggesting to upgrade to latest version, which is 1.5.16, which is
> compiled in jdk-11, should be able to compatible.}}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
