Search for packages
| purl | pkg:maven/org.ops4j.pax.logging/pax-logging-log4j2@1.11.7 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-8977-tjss-w7ba
Aliases: CVE-2021-45046 GHSA-7rjr-3q55-vv33 |
Incomplete fix for Apache Log4j vulnerability The fix to address [CVE-2021-44228](https://nvd.nist.gov/vuln/detail/CVE-2021-44228) in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allow attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in a remote code execution (RCE) attack. |
Affected by 2 other vulnerabilities. Affected by 2 other vulnerabilities. |
|
VCID-gnhu-4afv-pfhy
Aliases: GHSA-xxfh-x98p-j8fr GMS-2021-75 |
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in org.ops4j.pax.logging:pax-logging-log4j2. |
Affected by 3 other vulnerabilities. Affected by 3 other vulnerabilities. |
|
VCID-jwav-88m7-6fhz
Aliases: CVE-2021-44228 GHSA-jfh8-c2jp-5v3q |
Remote code injection in Log4j Log4j versions prior to 2.16.0 are subject to a remote code execution vulnerability via the ldap JNDI parser. As per [Apache's Log4j security guide](https://logging.apache.org/log4j/2.x/security.html): Apache Log4j2 <=2.14.1 JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.16.0, this behavior has been disabled by default. Log4j version 2.15.0 contained an earlier fix for the vulnerability, but that patch did not disable attacker-controlled JNDI lookups in all situations. For more information, see the `Updated advice for version 2.16.0` section of this advisory. |
Affected by 3 other vulnerabilities. Affected by 3 other vulnerabilities. |
|
VCID-r67p-yqg2-9bbq
Aliases: CVE-2021-44832 GHSA-8489-44mv-ggj8 |
Improper Input Validation and Injection in Apache Log4j2 Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to an attack where an attacker with permission to modify the logging configuration file can construct a malicious configuration using a JDBC Appender with a data source referencing a JNDI URI which can execute remote code. This issue is fixed by limiting JNDI data source names to the java protocol in Log4j2 versions 2.17.1, 2.12.4, and 2.3.2. |
Affected by 0 other vulnerabilities. Affected by 0 other vulnerabilities. |
|
VCID-sjuz-dd96-sqe3
Aliases: CVE-2021-45105 GHSA-p6xc-xr62-6r2g |
Uncontrolled Recursion This advisory has been marked as a false positive. |
Affected by 1 other vulnerability. Affected by 1 other vulnerability. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| This package is not known to fix vulnerabilities. | ||