Hi openMajun_admin, welcome to the openEuler Community.
I'm the Bot here serving you. You can find the instructions on how to interact with me at Here.
If you have any questions, please contact the SIG: sig-message-middleware, and any of the maintainers: @hu-zongtang , @jas0n918 , @dingwei-hello , any of the committers: @dingwei-hello , @sundapeng001 , @shilinlu
@hu-zongtang ,@jas0n918 ,@sundapeng001 ,@shilinlu ,@dingwei-2020
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-SP3(2.8.2):
4.openEuler-22.03-LTS-SP4(2.8.2):
5.openEuler-24.03-LTS(2.8.2):
6.openEuler-24.03-LTS-Next(2.8.2):
7.openEuler-24.03-LTS-SP1(2.8.2):
8.openEuler-24.03-LTS-SP2(2.8.2):
修复是否涉及abi变化(是/否)：
1.master(2.8.2):
2.openEuler-20.03-LTS-SP4(2.8.2):
3.openEuler-22.03-LTS-SP3(2.8.2):
4.openEuler-22.03-LTS-SP4(2.8.2):
5.openEuler-24.03-LTS(2.8.2):
6.openEuler-24.03-LTS-Next(2.8.2):
7.openEuler-24.03-LTS-SP1(2.8.2):
8.openEuler-24.03-LTS-SP2(2.8.2):
原因说明：
1.master(2.8.2):
2.openEuler-20.03-LTS-SP4(2.8.2):
3.openEuler-22.03-LTS-SP3(2.8.2):
4.openEuler-22.03-LTS-SP4(2.8.2):
5.openEuler-24.03-LTS(2.8.2):
6.openEuler-24.03-LTS-Next(2.8.2):
7.openEuler-24.03-LTS-SP1(2.8.2):
8.openEuler-24.03-LTS-SP2(2.8.2):
原因说明填写请参考下方表格(注意：版本是否受影响和版本的原因说明必须对应，例如master版本分支受影响，那原因说明只能是受影响对应的原因之一!)：
| 分支状态 | 原因说明 |
|---|---|
| 受影响 | 正常修复 |
| 受影响 | 暂不修复-漏洞仍在分析中 |
| 受影响 | 暂不修复-暂无解决方案或补丁 |
| 受影响 | 暂不修复-待升级版本修复 |
| 受影响 | 不修复-超出修复范围 |
| 受影响 | 不修复-特殊原因导致不再修复 |
| 不受影响 | 不受影响-组件不存在 |
| 不受影响 | 不受影响-已有内置的内联控制或缓解措施 |
| 不受影响 | 不受影响-漏洞代码不能被攻击者触发 |
| 不受影响 | 不受影响-漏洞代码不在执行路径 |
| 不受影响 | 不受影响-漏洞代码不存在 |
issue处理具体操作请参考:
https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
pr关联issue具体操作请参考:
https://gitee.com/help/articles/4142
经过cve-manager解析，(所有PR均已合入)
一、漏洞信息
漏洞编号：CVE-2023-44981
漏洞归属组件：kafka
漏洞归属的版本：2.4.0,2.8.2
CVSS评分：
BaseScore：9.1 Critical
Vector：CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
漏洞简述：
Authorization Bypass Through User-Controlled Key vulnerability in Apache ZooKeeper. If SASL Quorum Peer authentication is enabled in ZooKeeper (quorum.auth.enableSasl=true), the authorization is done by verifying that the instance part in SASL authentication ID is listed in zoo.cfg server list. The instance part in SASL auth ID is optional and if it s missing, like eve@EXAMPLE.COM , the authorization check will be skipped. As a result an arbitrary endpoint could join the cluster and begin propagating counterfeit changes to the leader, essentially giving it complete read-write access to the data tree. Quorum Peer authentication is not enabled by default.Users are recommended to upgrade to version 3.9.1, 3.8.3, 3.7.2, which fixes the issue.Alternately ensure the ensemble election/quorum communication is protected by a firewall as this will mitigate the issue.See the documentation for more details on correct cluster administration.
漏洞公开时间：2023-10-11 20:15:11
漏洞创建时间：2025-09-16 20:06:19
漏洞详情参考链接：
https://nvd.nist.gov/vuln/detail/CVE-2023-44981
更多参考(点击展开)
漏洞分析指导链接：
https://atomgit.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
漏洞数据来源:
其他
漏洞补丁信息：
详情(点击展开)
二、漏洞分析结构反馈
影响性分析说明：
Authorization Bypass Through User-Controlled Key vulnerability in Apache ZooKeeper. If SASL Quorum Peer authentication is enabled in ZooKeeper (quorum.auth.enableSasl=true), the authorization is done by verifying that the instance part in SASL authentication ID is listed in zoo.cfg server list. The instance part in SASL auth ID is optional and if it s missing, like
openEuler评分：
9.1
Vector：CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
受影响版本排查(受影响/不受影响)：
1.master(2.8.2):受影响
2.openEuler-20.03-LTS-SP4(2.8.2):受影响
3.openEuler-22.03-LTS-SP3(2.8.2):受影响
4.openEuler-22.03-LTS-SP4(2.8.2):受影响
5.openEuler-24.03-LTS(2.8.2):受影响
6.openEuler-24.03-LTS-Next(2.8.2):受影响
7.openEuler-24.03-LTS-SP1(2.8.2):受影响
8.openEuler-24.03-LTS-SP2(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-SP3(2.8.2):否
4.openEuler-22.03-LTS-SP4(2.8.2):是
5.openEuler-24.03-LTS(2.8.2):否
6.openEuler-24.03-LTS-Next(2.8.2):是
7.openEuler-24.03-LTS-SP1(2.8.2):是
8.openEuler-24.03-LTS-SP2(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-SP3(2.8.2):不修复-超出修复范围
4.openEuler-22.03-LTS-SP4(2.8.2):正常修复
5.openEuler-24.03-LTS(2.8.2):不修复-超出修复范围
6.openEuler-24.03-LTS-Next(2.8.2):正常修复
7.openEuler-24.03-LTS-SP1(2.8.2):正常修复
8.openEuler-24.03-LTS-SP2(2.8.2):不修复-超出修复范围
9.openEuler-24.03-LTS-SP3(2.8.2):正常修复
10.openEuler-24.03-LTS-SP4(2.8.2):正常修复