Skip to content

Commit c7f290a

Browse files

File tree

6 files changed

+297
-164
lines changed

6 files changed

+297
-164
lines changed
Lines changed: 101 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,101 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-445c-vh5m-36rj",
4+
"modified": "2026-04-14T00:13:29Z",
5+
"published": "2026-04-10T18:31:17Z",
6+
"aliases": [
7+
"CVE-2026-34478"
8+
],
9+
"summary": "Apache Log4j Core: log injection in `Rfc5424Layout` due to silent configuration incompatibility",
10+
"details": "Apache Log4j Core's [`Rfc5424Layout`](https://logging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout), in versions 2.21.0 through 2.25.3, is vulnerable to log injection via CRLF sequences due to undocumented renames of security-relevant configuration attributes.\n\nTwo distinct issues affect users of stream-based syslog services who configure Rfc5424Layout directly:\n\n * The `newLineEscape` attribute was silently renamed, causing newline escaping to stop working for users of TCP framing (RFC 6587), exposing them to CRLF injection in log output.\n * The `useTlsMessageFormat` attribute was silently renamed, causing users of TLS framing (RFC 5425) to be silently downgraded to unframed TCP (RFC 6587), without newline escaping.\n\nUsers of the `SyslogAppender` are not affected, as its configuration attributes were not modified.\n\nUsers are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue.",
11+
"severity": [
12+
{
13+
"type": "CVSS_V4",
14+
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N"
15+
}
16+
],
17+
"affected": [
18+
{
19+
"package": {
20+
"ecosystem": "Maven",
21+
"name": "org.apache.logging.log4j:log4j-core"
22+
},
23+
"ranges": [
24+
{
25+
"type": "ECOSYSTEM",
26+
"events": [
27+
{
28+
"introduced": "2.21.0"
29+
},
30+
{
31+
"fixed": "2.25.4"
32+
}
33+
]
34+
}
35+
]
36+
},
37+
{
38+
"package": {
39+
"ecosystem": "Maven",
40+
"name": "org.apache.logging.log4j:log4j-core"
41+
},
42+
"ranges": [
43+
{
44+
"type": "ECOSYSTEM",
45+
"events": [
46+
{
47+
"introduced": "3.0.0-beta1"
48+
},
49+
{
50+
"last_affected": "3.0.0-beta3"
51+
}
52+
]
53+
}
54+
]
55+
}
56+
],
57+
"references": [
58+
{
59+
"type": "ADVISORY",
60+
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-34478"
61+
},
62+
{
63+
"type": "WEB",
64+
"url": "https://github.com/apache/logging-log4j2/pull/4074"
65+
},
66+
{
67+
"type": "PACKAGE",
68+
"url": "https://github.com/apache/logging-log4j2"
69+
},
70+
{
71+
"type": "WEB",
72+
"url": "https://lists.apache.org/thread/3k1clr2l6vkdnl4cbhjrnt1nyjvb5gwt"
73+
},
74+
{
75+
"type": "WEB",
76+
"url": "https://logging.apache.org/cyclonedx/vdr.xml"
77+
},
78+
{
79+
"type": "WEB",
80+
"url": "https://logging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout"
81+
},
82+
{
83+
"type": "WEB",
84+
"url": "https://logging.apache.org/security.html#CVE-2026-34478"
85+
},
86+
{
87+
"type": "WEB",
88+
"url": "http://www.openwall.com/lists/oss-security/2026/04/10/7"
89+
}
90+
],
91+
"database_specific": {
92+
"cwe_ids": [
93+
"CWE-117",
94+
"CWE-684"
95+
],
96+
"severity": "MODERATE",
97+
"github_reviewed": true,
98+
"github_reviewed_at": "2026-04-14T00:13:29Z",
99+
"nvd_published_at": "2026-04-10T16:16:31Z"
100+
}
101+
}
Lines changed: 96 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,96 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-6hg6-v5c8-fphq",
4+
"modified": "2026-04-14T00:11:55Z",
5+
"published": "2026-04-10T18:31:17Z",
6+
"aliases": [
7+
"CVE-2026-34477"
8+
],
9+
"summary": "Apache Log4j Core: `verifyHostName` attribute silently ignored in TLS configuration",
10+
"details": "The fix for CVE-2025-68161 was incomplete: it addressed hostname verification only when enabled via the [`log4j2.sslVerifyHostName`](https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName) system property, but not when configured through the [`verifyHostName`](https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName) attribute of the `<Ssl>` element.\n\nAlthough the `verifyHostName` configuration attribute was introduced in Log4j Core 2.12.0, it was silently ignored in all versions through 2.25.3, leaving TLS connections vulnerable to interception regardless of the configured value.\n\nA network-based attacker may be able to perform a man-in-the-middle attack when all of the following conditions are met:\n\n * An SMTP, Socket, or Syslog appender is in use.\n * TLS is configured via a nested <Ssl> element.\n * The attacker can present a certificate issued by a CA trusted by the appender's configured trust store, or by the default Java trust store if none is configured.\n\nThis issue does not affect users of the HTTP appender, which uses a separate [`verifyHostname`](https://logging.apache.org/log4j/2.x/manual/appenders/network.html#HttpAppender-attr-verifyHostName) attribute that was not subject to this bug and verifies host names by default.\n\nUsers are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue.",
11+
"severity": [
12+
{
13+
"type": "CVSS_V4",
14+
"score": "CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:L/SA:N"
15+
}
16+
],
17+
"affected": [
18+
{
19+
"package": {
20+
"ecosystem": "Maven",
21+
"name": "org.apache.logging.log4j:log4j-core"
22+
},
23+
"ranges": [
24+
{
25+
"type": "ECOSYSTEM",
26+
"events": [
27+
{
28+
"introduced": "2.12.0"
29+
},
30+
{
31+
"fixed": "2.25.4"
32+
}
33+
]
34+
}
35+
]
36+
},
37+
{
38+
"package": {
39+
"ecosystem": "Maven",
40+
"name": "org.apache.logging.log4j:log4j-core"
41+
},
42+
"ranges": [
43+
{
44+
"type": "ECOSYSTEM",
45+
"events": [
46+
{
47+
"introduced": "3.0.0-alpha1"
48+
},
49+
{
50+
"last_affected": "3.0.0-beta3"
51+
}
52+
]
53+
}
54+
]
55+
}
56+
],
57+
"references": [
58+
{
59+
"type": "ADVISORY",
60+
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-34477"
61+
},
62+
{
63+
"type": "WEB",
64+
"url": "https://github.com/apache/logging-log4j2/pull/4075"
65+
},
66+
{
67+
"type": "PACKAGE",
68+
"url": "https://github.com/apache/logging-log4j2"
69+
},
70+
{
71+
"type": "WEB",
72+
"url": "https://lists.apache.org/thread/lkx8cl46t2bvkcwfcb2pd43ygc097lq4"
73+
},
74+
{
75+
"type": "WEB",
76+
"url": "https://logging.apache.org/cyclonedx/vdr.xml"
77+
},
78+
{
79+
"type": "WEB",
80+
"url": "https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName"
81+
},
82+
{
83+
"type": "WEB",
84+
"url": "https://logging.apache.org/security.html#CVE-2026-34477"
85+
}
86+
],
87+
"database_specific": {
88+
"cwe_ids": [
89+
"CWE-297"
90+
],
91+
"severity": "MODERATE",
92+
"github_reviewed": true,
93+
"github_reviewed_at": "2026-04-14T00:11:55Z",
94+
"nvd_published_at": "2026-04-10T16:16:30Z"
95+
}
96+
}
Lines changed: 100 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,100 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-h383-gmxw-35v2",
4+
"modified": "2026-04-14T00:10:59Z",
5+
"published": "2026-04-10T18:31:18Z",
6+
"aliases": [
7+
"CVE-2026-34479"
8+
],
9+
"summary": "Apache Log4j 1 to Log4j 2 bridge: silent log event loss in Log4j1XmlLayout due to unescaped XML 1.0 forbidden characters",
10+
"details": "The `Log4j1XmlLayout` from the Apache Log4j 1-to-Log4j 2 bridge fails to escape characters forbidden by the XML 1.0 standard, producing malformed XML output. Conforming XML parsers are required to reject documents containing such characters with a fatal error, which may cause downstream log processing systems to drop or fail to index affected records.\n\nTwo groups of users are affected:\n\n* Those using `Log4j1XmlLayout` directly in a Log4j Core 2 configuration file.\n* Those using the Log4j 1 configuration compatibility layer with `org.apache.log4j.xml.XMLLayout` specified as the layout class.\n\nUsers are advised to upgrade to Apache Log4j 1-to-Log4j 2 bridge version `2.25.4`, which corrects this issue.\n\n> [!NOTE]\n> The Apache Log4j 1-to-Log4j 2 bridge is deprecated and will not be present in Log4j 3. Users are encouraged to consult the\n> [Log4j 1 to Log4j 2 migration guide](https://logging.apache.org/log4j/2.x/migrate-from-log4j1.html), and specifically the section on eliminating reliance on the bridge.",
11+
"severity": [
12+
{
13+
"type": "CVSS_V4",
14+
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N"
15+
}
16+
],
17+
"affected": [
18+
{
19+
"package": {
20+
"ecosystem": "Maven",
21+
"name": "org.apache.logging.log4j:log4j-1.2-api"
22+
},
23+
"ranges": [
24+
{
25+
"type": "ECOSYSTEM",
26+
"events": [
27+
{
28+
"introduced": "2.7"
29+
},
30+
{
31+
"fixed": "2.25.4"
32+
}
33+
]
34+
}
35+
]
36+
},
37+
{
38+
"package": {
39+
"ecosystem": "Maven",
40+
"name": "org.apache.logging.log4j:log4j-1.2-api"
41+
},
42+
"ranges": [
43+
{
44+
"type": "ECOSYSTEM",
45+
"events": [
46+
{
47+
"introduced": "3.0.0-beta1"
48+
},
49+
{
50+
"last_affected": "3.0.0-beta2"
51+
}
52+
]
53+
}
54+
]
55+
}
56+
],
57+
"references": [
58+
{
59+
"type": "ADVISORY",
60+
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-34479"
61+
},
62+
{
63+
"type": "WEB",
64+
"url": "https://github.com/apache/logging-log4j2/pull/4078"
65+
},
66+
{
67+
"type": "PACKAGE",
68+
"url": "https://github.com/apache/logging-log4j2"
69+
},
70+
{
71+
"type": "WEB",
72+
"url": "https://lists.apache.org/thread/gd0hp6mj17rn3kj279vgy4p7kd4zz5on"
73+
},
74+
{
75+
"type": "WEB",
76+
"url": "https://logging.apache.org/cyclonedx/vdr.xml"
77+
},
78+
{
79+
"type": "WEB",
80+
"url": "https://logging.apache.org/log4j/2.x/migrate-from-log4j1.html"
81+
},
82+
{
83+
"type": "WEB",
84+
"url": "https://logging.apache.org/security.html#CVE-2026-34479"
85+
},
86+
{
87+
"type": "WEB",
88+
"url": "http://www.openwall.com/lists/oss-security/2026/04/10/8"
89+
}
90+
],
91+
"database_specific": {
92+
"cwe_ids": [
93+
"CWE-116"
94+
],
95+
"severity": "MODERATE",
96+
"github_reviewed": true,
97+
"github_reviewed_at": "2026-04-14T00:10:59Z",
98+
"nvd_published_at": "2026-04-10T16:16:31Z"
99+
}
100+
}

advisories/unreviewed/2026/04/GHSA-445c-vh5m-36rj/GHSA-445c-vh5m-36rj.json

Lines changed: 0 additions & 56 deletions
This file was deleted.

0 commit comments

Comments
 (0)