Количество 8
Количество 8
CVE-2025-68161
The Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not perform TLS hostname verification of the peer certificate, even when the verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName configuration attribute or the log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName system property is set to true. This issue may allow a man-in-the-middle attacker to intercept or redirect log traffic under the following conditions: * The attacker is able to intercept or redirect network traffic between the client and the log receiver. * The attacker can present a server certificate issued by a certification authority trusted by the Socket Appender’s configured trust store (or by the default Java trust store if no custom trust store is configured). Users are advised to upgrade to Apache Log4j Core version 2.25.3, which addresses this issue. A...
CVE-2025-68161
The Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not perform TLS hostname verification of the peer certificate, even when the verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName configuration attribute or the log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName system property is set to true. This issue may allow a man-in-the-middle attacker to intercept or redirect log traffic under the following conditions: * The attacker is able to intercept or redirect network traffic between the client and the log receiver. * The attacker can present a server certificate issued by a certification authority trusted by the Socket Appender’s configured trust store (or by the default Java trust store if no custom trust store is configured). Users are advised to upgrade to Apache Log4j Core version 2.25.3, which addresses this i
CVE-2025-68161
Apache Log4j Core: Missing TLS hostname verification in Socket appender
CVE-2025-68161
The Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2. ...
SUSE-SU-2026:0254-1
Security update for log4j
GHSA-vc5p-v9hr-52mj
Apache Log4j does not verify the TLS hostname in its Socket Appender
BDU:2026-00009
Уязвимость компонента Socket Appender реализации API библиотеки журналирования Apache Log4j Core, позволяющая нарушителю перехватить трафик журнала
openSUSE-SU-2026:20099-1
Security update for coredns
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2025-68161 The Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not perform TLS hostname verification of the peer certificate, even when the verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName configuration attribute or the log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName system property is set to true. This issue may allow a man-in-the-middle attacker to intercept or redirect log traffic under the following conditions: * The attacker is able to intercept or redirect network traffic between the client and the log receiver. * The attacker can present a server certificate issued by a certification authority trusted by the Socket Appender’s configured trust store (or by the default Java trust store if no custom trust store is configured). Users are advised to upgrade to Apache Log4j Core version 2.25.3, which addresses this issue. A... | CVSS3: 4.8 | 0% Низкий | около 2 месяцев назад | |
CVE-2025-68161 The Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not perform TLS hostname verification of the peer certificate, even when the verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName configuration attribute or the log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName system property is set to true. This issue may allow a man-in-the-middle attacker to intercept or redirect log traffic under the following conditions: * The attacker is able to intercept or redirect network traffic between the client and the log receiver. * The attacker can present a server certificate issued by a certification authority trusted by the Socket Appender’s configured trust store (or by the default Java trust store if no custom trust store is configured). Users are advised to upgrade to Apache Log4j Core version 2.25.3, which addresses this i | CVSS3: 4.8 | 0% Низкий | около 2 месяцев назад | |
CVE-2025-68161 Apache Log4j Core: Missing TLS hostname verification in Socket appender | 0% Низкий | около 2 месяцев назад | ||
CVE-2025-68161 The Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2. ... | CVSS3: 4.8 | 0% Низкий | около 2 месяцев назад | |
SUSE-SU-2026:0254-1 Security update for log4j | 0% Низкий | 13 дней назад | ||
GHSA-vc5p-v9hr-52mj Apache Log4j does not verify the TLS hostname in its Socket Appender | 0% Низкий | около 2 месяцев назад | ||
BDU:2026-00009 Уязвимость компонента Socket Appender реализации API библиотеки журналирования Apache Log4j Core, позволяющая нарушителю перехватить трафик журнала | CVSS3: 4 | 0% Низкий | около 2 месяцев назад | |
openSUSE-SU-2026:20099-1 Security update for coredns | 11 дней назад |
Уязвимостей на страницу