Star0
6
代码
代码
Issues8
Pull Requests1
项目讨论
Wiki
分析
Star0
6
已关闭
CVE-2022-23305 #10
openeuler-ci-bot创建于  2024年8月20日关闭于  8 天前
openeuler-ci-bot
openeuler-ci-bot成员
2024年8月20日 创建

一、漏洞信息
漏洞编号：CVE-2022-23305
漏洞归属组件：kafka
漏洞归属的版本：2.4.0,2.6.0,2.8.1,2.8.2
CVSS评分：
BaseScore：9.8 Critical
Vector：CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
漏洞简述：
By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
漏洞公开时间：2022-01-19 00:15:08
漏洞创建时间：2024-08-20 11:32:57
漏洞详情参考链接：
https://nvd.nist.gov/vuln/detail/CVE-2022-23305

更多参考(点击展开)

无

漏洞分析指导链接：
https://atomgit.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
漏洞数据来源:
openBrain开源漏洞感知系统
漏洞补丁信息：

详情(点击展开)

无

二、漏洞分析结构反馈
影响性分析说明：
By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
openEuler评分：
9.8
Vector：CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
受影响版本排查(受影响/不受影响)：
1.master(2.8.2):受影响
2.openEuler-20.03-LTS-SP4(2.8.2):受影响
3.openEuler-22.03-LTS-SP1(2.8.2):受影响
4.openEuler-22.03-LTS-SP3(2.8.2):受影响
5.openEuler-22.03-LTS-SP4(2.8.2):受影响
6.openEuler-24.03-LTS(2.8.2):受影响
7.openEuler-24.03-LTS-Next(2.8.2):受影响
8.openEuler-24.03-LTS-SP1(2.8.2):受影响
9.openEuler-24.03-LTS-SP3(2.8.2):受影响
10.openEuler-24.03-LTS-SP4(2.8.2):受影响

修复是否涉及abi变化(是/否)：
1.master(2.8.2):是
2.openEuler-20.03-LTS-SP4(2.8.2):是
3.openEuler-22.03-LTS-SP1(2.8.2):否
4.openEuler-22.03-LTS-SP3(2.8.2):否
5.openEuler-22.03-LTS-SP4(2.8.2):是
6.openEuler-24.03-LTS(2.8.2):否
7.openEuler-24.03-LTS-Next(2.8.2):是
8.openEuler-24.03-LTS-SP1(2.8.2):是
9.openEuler-24.03-LTS-SP3(2.8.2):是
10.openEuler-24.03-LTS-SP4(2.8.2):是

原因说明：
1.master(2.8.2):正常修复
2.openEuler-20.03-LTS-SP4(2.8.2):正常修复
3.openEuler-22.03-LTS-SP4(2.8.2):正常修复
4.openEuler-24.03-LTS-Next(2.8.2):正常修复
5.openEuler-24.03-LTS-SP1(2.8.2):正常修复
6.openEuler-24.03-LTS-SP3(2.8.2):正常修复
7.openEuler-24.03-LTS-SP4(2.8.2):正常修复
8.openEuler-22.03-LTS-SP1(2.8.2):不修复-超出修复范围
9.openEuler-22.03-LTS-SP3(2.8.2):不修复-超出修复范围
10.openEuler-24.03-LTS(2.8.2):不修复-超出修复范围

likedislike
openeuler-ci-botopeneuler-ci-bot成员
2024年8月20日 添加了   CVE/UNFIXED 标签
openeuler-ci-botopeneuler-ci-bot成员
2024年8月20日 创建了CVE和安全问题
openeuler-ci-bot
openeuler-ci-bot成员
2024年8月20日 评论：

@hu-zongtang ,@jas0n918 ,@dingwei-hello ,@sundapeng001 ,@shilinlu
issue处理注意事项:
1. 当前issue受影响的分支提交pr时, 须在pr描述中填写当前issue编号进行关联, 否则无法关闭当前issue;
2. 模板内容需要填写完整, 无论是受影响或者不受影响都需要填写完整内容,未引入的分支不需要填写, 否则无法关闭当前issue;
3. 以下为模板中需要填写完整的内容, 请复制到评论区回复, 注: 内容的标题名称(影响性分析说明, openEuler评分, 受影响版本排查(受影响/不受影响), 修复是否涉及abi变化(是/否))不能省略,省略后cve-manager将无法正常解析填写内容.

影响性分析说明:

openEuler评分: (评分和向量)

受影响版本排查(受影响/不受影响):
1.master(2.8.2):
2.openEuler-20.03-LTS-SP4(2.8.2):
3.openEuler-22.03-LTS-SP1(2.8.2):
4.openEuler-22.03-LTS-SP3(2.8.2):
5.openEuler-22.03-LTS-SP4(2.8.2):
6.openEuler-24.03-LTS(2.8.2):
7.openEuler-24.03-LTS-Next(2.8.2):

修复是否涉及abi变化(是/否)：
1.master(2.8.2):
2.openEuler-20.03-LTS-SP4(2.8.2):
3.openEuler-22.03-LTS-SP1(2.8.2):
4.openEuler-22.03-LTS-SP3(2.8.2):
5.openEuler-22.03-LTS-SP4(2.8.2):
6.openEuler-24.03-LTS(2.8.2):
7.openEuler-24.03-LTS-Next(2.8.2):

issue处理具体操作请参考:
https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
pr关联issue具体操作请参考:
https://gitee.com/help/articles/4142

likedislike
openeuler-ci-botopeneuler-ci-bot成员
2024年8月20日 添加了   sig/sig-message-midd 标签
openeuler-ci-bot
openeuler-ci-bot成员
2024年8月20日 评论：
参考网址 关联pr 状态 补丁链接
https://nvd.nist.gov/vuln/detail/CVE-2022-23305
https://ubuntu.com/security/CVE-2022-23305NoneNonehttps://discourse.ubuntu.com/c/ubuntu-pro
https://www.opencve.io/cve/CVE-2022-23305
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2022-23305
https://security-tracker.debian.org/tracker/CVE-2022-23305

说明：补丁链接仅供初步排查参考，实际可用性请人工再次确认，补丁下载验证可使用CVE补丁工具。
若补丁不准确，烦请在此issue下评论 '/report-patch 参考网址 补丁链接1,补丁链接2' 反馈正确信息，便于我们不断优化工具，不胜感激。
如 /report-patch https://security-tracker.debian.org/tracker/CVE-2021-3997 https://github.com/systemd/systemd/commit/5b1cf7a9be37e20133c0208005274ce4a5b5c6a1

likedislike
openeuler-ci-botopeneuler-ci-bot成员
2024年8月21日 将计划开始日期设置为2024-08-21
此处折叠了11条事件消息 查看更多
openeuler-ci-botopeneuler-ci-bot成员
2024年10月10日 修改了描述
W
weiwei1234_nickname
2025年1月21日 评论：

/reason 测试环境创建的issue

likedislike
openeuler-ci-botopeneuler-ci-bot成员
2025年10月27日 修改了描述
openeuler-ci-botopeneuler-ci-bot成员
2025年11月5日 修改了描述
yanzhicong1yanzhicong1
9月11日 关联了pull request：[Fix] Fix CVE-2022-23305 and CVE-2023-44981 in kafka by backporting the upstream patch and upgraded version
yanzhicong1yanzhicong1
9月11日 关联了pull request：[Fix] Fix CVE-2022-23305 and CVE-2023-44981 in kafka by backporting the upstream patch and upgraded version
yanzhicong1
yanzhicong1
9月20日 评论：

影响性分析说明：

openEuler评分：
9.8
Vector：CVSS：3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

likedislike
openeuler-ci-botopeneuler-ci-bot成员
9月20日 修改了issue 的描述
openeuler-ci-bot
openeuler-ci-bot成员
9月20日 评论：

经过cve-manager解析，部分字段填写错误，如红色字体所示：

影响性分析说明:
(请填写此字段)

openEuler评分: (评分和向量)
9.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

受影响版本排查(受影响/不受影响):
1.master:(请填写此字段)
2.openEuler-20.03-LTS-SP4:(请填写此字段)
3.openEuler-22.03-LTS-SP1:(请填写此字段)
4.openEuler-22.03-LTS-SP3:(请填写此字段)
5.openEuler-22.03-LTS-SP4:(请填写此字段)
6.openEuler-24.03-LTS:(请填写此字段)
7.openEuler-24.03-LTS-Next:(请填写此字段)
8.openEuler-24.03-LTS-SP1:(请填写此字段)
9.openEuler-24.03-LTS-SP3:(请填写此字段)
10.openEuler-24.03-LTS-SP4:(请填写此字段)

修复是否涉及abi变化(是/否)：
1.master:(请填写此字段)
2.openEuler-20.03-LTS-SP4:(请填写此字段)
3.openEuler-22.03-LTS-SP1:(请填写此字段)
4.openEuler-22.03-LTS-SP3:(请填写此字段)
5.openEuler-22.03-LTS-SP4:(请填写此字段)
6.openEuler-24.03-LTS:(请填写此字段)
7.openEuler-24.03-LTS-Next:(请填写此字段)
8.openEuler-24.03-LTS-SP1:(请填写此字段)
9.openEuler-24.03-LTS-SP3:(请填写此字段)
10.openEuler-24.03-LTS-SP4:(请填写此字段)

原因说明：

likedislike
yanzhicong1yanzhicong1
9月20日 关联了pull request：[Fix] Fix CVE-2022-23302 and CVE-2022-23305 and CVE-2022-23307 and CVE-2023-44981 and CVE-2024-23944 and CVE-2024-31141 and CVE-2024-56128 and CVE-2025-27818 and CVE-2025-27819
yanzhicong1yanzhicong1
9月20日 关联了pull request：[Fix] Fix CVE-2022-23302 and CVE-2022-23305 and CVE-2022-23307 and CVE-2023-44981 and CVE-2024-23944 and CVE-2024-31141 and CVE-2024-56128 and CVE-2025-27818 and CVE-2025-27819
yanzhicong1
yanzhicong1
9月20日 评论：

/check-issue

likedislike
openeuler-ci-bot
openeuler-ci-bot成员
9月20日 评论：

经过cve-manager解析，部分字段填写错误，如红色字体所示：

影响性分析说明:
(请填写此字段)

openEuler评分: (评分和向量)
9.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

受影响版本排查(受影响/不受影响):
1.master:(请填写此字段)
2.openEuler-20.03-LTS-SP4:(请填写此字段)
3.openEuler-22.03-LTS-SP1:(请填写此字段)
4.openEuler-22.03-LTS-SP3:(请填写此字段)
5.openEuler-22.03-LTS-SP4:(请填写此字段)
6.openEuler-24.03-LTS:(请填写此字段)
7.openEuler-24.03-LTS-Next:(请填写此字段)
8.openEuler-24.03-LTS-SP1:(请填写此字段)
9.openEuler-24.03-LTS-SP3:(请填写此字段)
10.openEuler-24.03-LTS-SP4:(请填写此字段)

修复是否涉及abi变化(是/否)：
1.master:(请填写此字段)
2.openEuler-20.03-LTS-SP4:(请填写此字段)
3.openEuler-22.03-LTS-SP1:(请填写此字段)
4.openEuler-22.03-LTS-SP3:(请填写此字段)
5.openEuler-22.03-LTS-SP4:(请填写此字段)
6.openEuler-24.03-LTS:(请填写此字段)
7.openEuler-24.03-LTS-Next:(请填写此字段)
8.openEuler-24.03-LTS-SP1:(请填写此字段)
9.openEuler-24.03-LTS-SP3:(请填写此字段)
10.openEuler-24.03-LTS-SP4:(请填写此字段)

原因说明：
1.master:(请填写此字段)
2.openEuler-20.03-LTS-SP4:(请填写此字段)
3.openEuler-22.03-LTS-SP4:(请填写此字段)
4.openEuler-24.03-LTS-Next:(请填写此字段)
5.openEuler-24.03-LTS-SP1:(请填写此字段)
6.openEuler-24.03-LTS-SP3:(请填写此字段)
7.openEuler-24.03-LTS-SP4:(请填写此字段)

likedislike
yanzhicong1
yanzhicong1
9月20日 评论：

影响性分析说明:
By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.

openEuler评分: (评分和向量)
9.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

受影响版本排查(受影响/不受影响):

1.master:受影响
2.openEuler-20.03-LTS-SP4:受影响
3.openEuler-22.03-LTS-SP1:受影响
4.openEuler-22.03-LTS-SP3:受影响
5.openEuler-22.03-LTS-SP4:受影响
6.openEuler-24.03-LTS:受影响
7.openEuler-24.03-LTS-Next:受影响
8.openEuler-24.03-LTS-SP1:受影响
9.openEuler-24.03-LTS-SP3:受影响
10.openEuler-24.03-LTS-SP4:受影响

修复是否涉及abi变化(是/否)：

1.master:是
2.openEuler-20.03-LTS-SP4:是
3.openEuler-22.03-LTS-SP1:否
4.openEuler-22.03-LTS-SP3:否
5.openEuler-22.03-LTS-SP4:是
6.openEuler-24.03-LTS:否
7.openEuler-24.03-LTS-Next:是
8.openEuler-24.03-LTS-SP1:是
9.openEuler-24.03-LTS-SP3:是
10.openEuler-24.03-LTS-SP4:是

原因说明：

1.master:正常修复
2.openEuler-20.03-LTS-SP4:正常修复
3.openEuler-22.03-LTS-SP1:不修复-超出修复范围
4.openEuler-22.03-LTS-SP3:不修复-超出修复范围
5.openEuler-22.03-LTS-SP4:正常修复
6.openEuler-24.03-LTS:不修复-超出修复范围
7.openEuler-24.03-LTS-Next:正常修复
8.openEuler-24.03-LTS-SP1:正常修复
9.openEuler-24.03-LTS-SP3:正常修复
10.openEuler-24.03-LTS-SP4:正常修复

likedislike
openeuler-ci-botopeneuler-ci-bot成员
9月20日 修改了issue 的描述
openeuler-ci-bot
openeuler-ci-bot成员
9月20日 评论：

@ 经过 cve-manager 解析, 已分析的内容如下表所示:

状态 分析项目 内容
已分析 1.影响性分析说明 By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
已分析 2.openEulerScore 9.8
已分析 3.openEulerVector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
已分析 4.受影响版本排查 master:受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP1:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-22.03-LTS-SP4:受影响,openEuler-24.03-LTS:受影响,openEuler-24.03-LTS-Next:受影响,openEuler-24.03-LTS-SP1:受影响,openEuler-24.03-LTS-SP3:受影响,openEuler-24.03-LTS-SP4:受影响
已分析 5.是否涉及abi变化 master:是,openEuler-20.03-LTS-SP4:是,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP3:否,openEuler-22.03-LTS-SP4:是,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:是,openEuler-24.03-LTS-SP1:是,openEuler-24.03-LTS-SP3:是,openEuler-24.03-LTS-SP4:是
已分析 6.原因说明 master:正常修复,openEuler-20.03-LTS-SP4:正常修复,openEuler-22.03-LTS-SP4:正常修复,openEuler-24.03-LTS-Next:正常修复,openEuler-24.03-LTS-SP1:正常修复,openEuler-24.03-LTS-SP3:正常修复,openEuler-24.03-LTS-SP4:正常修复,openEuler-22.03-LTS-SP1:不修复-超出修复范围,openEuler-22.03-LTS-SP3:不修复-超出修复范围,openEuler-24.03-LTS:不修复-超出修复范围

请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.

likedislike
openeuler-ci-bot
openeuler-ci-bot成员
9月20日 评论：

经过cve-manager解析，部分分支PR未合入，如红色字体所示：

原因说明：
1.master:正常修复(PR未合入)
2.openEuler-20.03-LTS-SP4:正常修复(PR未合入)
3.openEuler-22.03-LTS-SP4:正常修复(PR未合入)
4.openEuler-24.03-LTS-Next:正常修复(PR未合入)
5.openEuler-24.03-LTS-SP1:正常修复(PR未合入)
6.openEuler-24.03-LTS-SP3:正常修复(PR未合入)
7.openEuler-24.03-LTS-SP4:正常修复(PR未合入)
8.openEuler-22.03-LTS-SP1:不修复-超出修复范围
9.openEuler-22.03-LTS-SP3:不修复-超出修复范围
10.openEuler-24.03-LTS:不修复-超出修复范围

likedislike
openeuler-ci-botopeneuler-ci-bot成员
9月20日 issue状态由 待办的 改变为 进行中
I
infra_team
9月21日 评论：

🔍 CVE 项目匹配性分析结果

CVE: CVE-2022-23305

针对分支: master

结果: ❌ 不匹配

原因: CVE 真实存在（NVD totalResults=1、MITRE state=PUBLISHED、GitHub Advisory GHSA-65fg-84f6-3jq3），但受影响组件是 Apache Log4j 1.x 的 JDBCAppender（SQL 注入），NVD/MITRE/GHSA 三个来源的受影响产品均为 log4j（CPE: cpe:2.3🅰️apache:log4j 1.2.x）及 reload4j<1.2.18.2，均不含 kafka。CVE-2022-23305 是 log4j 1.x 组件自身的漏洞，修复应归属 log4j/reload4j 软件包，与本项目包名 kafka 不匹配。Issue 中列出的 kafka 版本(2.4.0/2.6.0/2.8.1/2.8.2)是 openBrain 因 kafka 构建依赖 log4j 1.x 而自动归因的结果，且该漏洞仅在显式配置 JDBCAppender 时才可利用（非默认配置），并非 kafka 代码自身漏洞。归属判断：组件不匹配 → NOT_MATCHED

建议:

  • 此 CVE 实际影响的项目与当前 Issue 所在项目不一致
  • 建议关闭此 Issue，或将其移至正确项目的 Issue 列表
  • 如有疑问，请联系安全团队确认

此评论由 Claude Agent Team（项目经理）自动生成

likedislike
JR.HaleJR.Hale
9 天前 关联了pull request：[Fix] Fix CVE-2022-23302 and CVE-2022-23305 and CVE-2022-23307 and CVE-2023-44981 and CVE-2024-23944 and CVE-2024-31141 and CVE-2024-56128 and CVE-2025-27818 and CVE-2025-27819
JR.HaleJR.Hale
9 天前 关联了pull request：[Fix] Fix CVE-2022-23302 and CVE-2022-23305 and CVE-2022-23307 and CVE-2023-44981 and CVE-2024-23944 and CVE-2024-31141 and CVE-2024-56128 and CVE-2025-27818 and CVE-2025-27819
openeuler-ci-botopeneuler-ci-bot成员
9 天前 关联了pull request：[sync] PR-90: [Fix] Fix CVE-2022-23302 and CVE-2022-23305 and CVE-2022-23307 and CVE-2023-44981 and CVE-2024-23944 and CVE-2024-31141 and CVE-2024-56128 and CVE-2025-27818 and CVE-2025-27819
openeuler-ci-botopeneuler-ci-bot成员
8 天前 关联了pull request：[sync] PR-90: [Fix] Fix CVE-2022-23302 and CVE-2022-23305 and CVE-2022-23307 and CVE-2023-44981 and CVE-2024-23944 and CVE-2024-31141 and CVE-2024-56128 and CVE-2025-27818 and CVE-2025-27819
openeuler-ci-botopeneuler-ci-bot成员
8 天前 关联了pull request：[sync] PR-91: [Fix] Fix CVE-2022-23302 and CVE-2022-23305 and CVE-2022-23307 and CVE-2023-44981 and CVE-2024-23944 and CVE-2024-31141 and CVE-2024-56128 and CVE-2025-27818 and CVE-2025-27819
openeuler-ci-botopeneuler-ci-bot成员
8 天前 关联了pull request：[sync] PR-90: [Fix] Fix CVE-2022-23302 and CVE-2022-23305 and CVE-2022-23307 and CVE-2023-44981 and CVE-2024-23944 and CVE-2024-31141 and CVE-2024-56128 and CVE-2025-27818 and CVE-2025-27819
JR.Hale
JR.Hale
8 天前 评论：

影响性分析说明:
By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.

openEuler评分: (评分和向量)
9.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

受影响版本排查(受影响/不受影响):

1.master:受影响
2.openEuler-20.03-LTS-SP4:受影响
3.openEuler-22.03-LTS-SP1:受影响
4.openEuler-22.03-LTS-SP3:受影响
5.openEuler-22.03-LTS-SP4:受影响
6.openEuler-24.03-LTS:受影响
7.openEuler-24.03-LTS-Next:受影响
8.openEuler-24.03-LTS-SP1:受影响
9.openEuler-24.03-LTS-SP3:受影响
10.openEuler-24.03-LTS-SP4:受影响

修复是否涉及abi变化(是/否)：

1.master:是
2.openEuler-20.03-LTS-SP4:是
3.openEuler-22.03-LTS-SP1:否
4.openEuler-22.03-LTS-SP3:否
5.openEuler-22.03-LTS-SP4:是
6.openEuler-24.03-LTS:否
7.openEuler-24.03-LTS-Next:是
8.openEuler-24.03-LTS-SP1:是
9.openEuler-24.03-LTS-SP3:是
10.openEuler-24.03-LTS-SP4:是

原因说明：

1.master:正常修复
2.openEuler-20.03-LTS-SP4:正常修复
3.openEuler-22.03-LTS-SP1:不修复-超出修复范围
4.openEuler-22.03-LTS-SP3:不修复-超出修复范围
5.openEuler-22.03-LTS-SP4:正常修复
6.openEuler-24.03-LTS:不修复-超出修复范围
7.openEuler-24.03-LTS-Next:正常修复
8.openEuler-24.03-LTS-SP1:正常修复
9.openEuler-24.03-LTS-SP3:正常修复
10.openEuler-24.03-LTS-SP4:正常修复

likedislike
openeuler-ci-bot
openeuler-ci-bot成员
8 天前 评论：

@ 经过 cve-manager 解析, 已分析的内容如下表所示:

状态 分析项目 内容
已分析 1.影响性分析说明 By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
已分析 2.openEulerScore 9.8
已分析 3.openEulerVector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
已分析 4.受影响版本排查 master:受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP1:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-22.03-LTS-SP4:受影响,openEuler-24.03-LTS:受影响,openEuler-24.03-LTS-Next:受影响,openEuler-24.03-LTS-SP1:受影响,openEuler-24.03-LTS-SP3:受影响,openEuler-24.03-LTS-SP4:受影响
已分析 5.是否涉及abi变化 master:是,openEuler-20.03-LTS-SP4:是,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP3:否,openEuler-22.03-LTS-SP4:是,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:是,openEuler-24.03-LTS-SP1:是,openEuler-24.03-LTS-SP3:是,openEuler-24.03-LTS-SP4:是
已分析 6.原因说明 master:正常修复,openEuler-20.03-LTS-SP4:正常修复,openEuler-22.03-LTS-SP4:正常修复,openEuler-24.03-LTS-Next:正常修复,openEuler-24.03-LTS-SP1:正常修复,openEuler-24.03-LTS-SP3:正常修复,openEuler-24.03-LTS-SP4:正常修复,openEuler-22.03-LTS-SP1:不修复-超出修复范围,openEuler-22.03-LTS-SP3:不修复-超出修复范围,openEuler-24.03-LTS:不修复-超出修复范围

请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.

likedislike
openeuler-ci-bot
openeuler-ci-bot成员
8 天前 评论：

经过cve-manager解析，(所有PR均已合入)

likedislike
openeuler-ci-botopeneuler-ci-bot成员
8 天前 issue状态由 进行中 改变为 已完成
openeuler-ci-botopeneuler-ci-bot成员
8 天前 关闭了 issue
openeuler-ci-bot
openeuler-ci-bot成员
8 天前 评论：

经过cve-manager解析，(所有PR均已合入)

likedislike
openeuler-ci-botopeneuler-ci-bot成员
8 天前 删除了label：CVE/UNFIXED
openeuler-ci-botopeneuler-ci-bot成员
8 天前 添加了label：CVE/FIXED