Hi openeuler-ci-bot, 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: Programming-language, and any of the maintainers: @Lostwayzxc , @Charlie_li , any of the committers: @lyn1001 , @randy1568 , @wk333
@Charlie_li ,@lyn1001 ,@Lostwayzxc ,@randy1568 ,@wk333
issue处理注意事项:
1. 当前issue受影响的分支提交pr时, 须在pr描述中填写当前issue编号进行关联, 否则无法关闭当前issue;
2. 模板内容需要填写完整, 无论是受影响或者不受影响都需要填写完整内容,未引入的分支不需要填写, 否则无法关闭当前issue;
3. 以下为模板中需要填写完整的内容, 请复制到评论区回复, 注: 内容的标题名称(影响性分析说明, openEuler评分, 受影响版本排查(受影响/不受影响), 修复是否涉及abi变化(是/否), 原因说明)不能省略,省略后cve-manager将无法正常解析填写内容.
影响性分析说明:
openEuler评分: (评分和向量)
受影响版本排查(受影响/不受影响):
1.master:
2.openEuler-20.03-LTS-SP4:
3.openEuler-22.03-LTS-SP3(2.16):
4.openEuler-22.03-LTS-SP4(2.16):
5.openEuler-24.03-LTS(2.1700):
6.openEuler-24.03-LTS-Next(2.1700):
7.openEuler-24.03-LTS-SP1(2.1700):
8.openEuler-24.03-LTS-SP2(2.1700):
修复是否涉及abi变化(是/否)：
1.master:
2.openEuler-20.03-LTS-SP4:
3.openEuler-22.03-LTS-SP3(2.16):
4.openEuler-22.03-LTS-SP4(2.16):
5.openEuler-24.03-LTS(2.1700):
6.openEuler-24.03-LTS-Next(2.1700):
7.openEuler-24.03-LTS-SP1(2.1700):
8.openEuler-24.03-LTS-SP2(2.1700):
原因说明：
1.master:
2.openEuler-20.03-LTS-SP4:
3.openEuler-22.03-LTS-SP3(2.16):
4.openEuler-22.03-LTS-SP4(2.16):
5.openEuler-24.03-LTS(2.1700):
6.openEuler-24.03-LTS-Next(2.1700):
7.openEuler-24.03-LTS-SP1(2.1700):
8.openEuler-24.03-LTS-SP2(2.1700):
原因说明填写请参考下方表格(注意：版本是否受影响和版本的原因说明必须对应，例如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 解析, 已分析的内容如下表所示:
| 状态 | 分析项目 | 内容 |
|---|---|---|
| 已分析 | 1.影响性分析说明 | Authen::SASL::Perl::DIGEST_MD5 versions 2.04 through 2.1800 for Perl generates the cnonce insecurely.The cnonce (client nonce) is generated from an MD5 hash of the PID, the epoch time and the built-in rand function. The PID will come from a small set of numbers, and the epoch time may be guessed, if it is not leaked from the HTTP Date header. The built-in rand function is unsuitable for cryptographic usage.According to RFC 2831, The cnonce-value is an opaque quoted string value provided by the client and used by both client and server to avoid chosen plaintext attacks, and to provide mutual authentication. The security of the implementation depends on a good choice. It is RECOMMENDED that it contain at least 64 bits of entropy. |
| 已分析 | 2.openEulerScore | 6.5 |
| 已分析 | 3.openEulerVector | AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
| 已分析 | 4.受影响版本排查 | master:受影响,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-SP2:受影响,openEuler-20.03-LTS-SP4:不受影响,openEuler-24.03-LTS-SP3:受影响,openEuler-24.03-LTS-SP4:受影响 |
| 已分析 | 5.是否涉及abi变化 | master:否,openEuler-20.03-LTS-SP4:否,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-SP2:否,openEuler-24.03-LTS-SP3:否,openEuler-24.03-LTS-SP4:否 |
| 已分析 | 6.原因说明 | master:正常修复,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-SP2:正常修复,openEuler-20.03-LTS-SP4:不受影响-组件不存在,openEuler-24.03-LTS-SP3:正常修复,openEuler-24.03-LTS-SP4:正常修复 |
请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.
一、漏洞信息
漏洞编号：CVE-2025-40918
漏洞归属组件：perl-Authen-SASL
漏洞归属的版本：2.16,2.1700
CVSS评分：
BaseScore：6.5 Medium
Vector：CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
漏洞简述：
Authen::SASL::Perl::DIGEST_MD5 versions 2.04 through 2.1800 for Perl generates the cnonce insecurely. The cnonce (client nonce) is generated from an MD5 hash of the PID, the epoch time and the built-in rand function. The PID comes from a small set of numbers, and the epoch time may be guessed if not leaked from the HTTP Date header. The built-in rand function is unsuitable for cryptographic usage. According to RFC 2831, the cnonce-value should be provided by the client and contain at least 64 bits of entropy to ensure security.
漏洞公开时间：2025-07-16 22:15:25
漏洞创建时间：2025-07-17 08:21:25
漏洞详情参考链接：
https://nvd.nist.gov/vuln/detail/CVE-2025-40918
更多参考(点击展开)
无
漏洞分析指导链接：
https://atomgit.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
漏洞数据来源:
七彩瞬析开源风险感知平台
漏洞补丁信息：
详情(点击展开)
无
二、漏洞分析结构反馈
影响性分析说明：
Authen::SASL::Perl::DIGEST_MD5 versions 2.04 through 2.1800 for Perl generates the cnonce insecurely.The cnonce (client nonce) is generated from an MD5 hash of the PID, the epoch time and the built-in rand function. The PID will come from a small set of numbers, and the epoch time may be guessed, if it is not leaked from the HTTP Date header. The built-in rand function is unsuitable for cryptographic usage.According to RFC 2831, The cnonce-value is an opaque quoted string value provided by the client and used by both client and server to avoid chosen plaintext attacks, and to provide mutual authentication. The security of the implementation depends on a good choice. It is RECOMMENDED that it contain at least 64 bits of entropy.
openEuler评分：
6.5
Vector：CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
受影响版本排查(受影响/不受影响)：
1.master(2.2000):受影响
2.openEuler-22.03-LTS-SP3(2.16):受影响
3.openEuler-22.03-LTS-SP4(2.16):受影响
4.openEuler-24.03-LTS(2.1700):受影响
5.openEuler-24.03-LTS-Next(2.1700):受影响
6.openEuler-24.03-LTS-SP1(2.1700):受影响
7.openEuler-24.03-LTS-SP2(2.1700):受影响
8.openEuler-20.03-LTS-SP4(2.16):不受影响
9.openEuler-24.03-LTS-SP3(2.1700):受影响
10.openEuler-24.03-LTS-SP4(2.1700):受影响
修复是否涉及abi变化(是/否)：
1.master(2.2000):否
2.openEuler-20.03-LTS-SP4(2.16):否
3.openEuler-22.03-LTS-SP3(2.16):否
4.openEuler-22.03-LTS-SP4(2.16):否
5.openEuler-24.03-LTS(2.1700):否
6.openEuler-24.03-LTS-Next(2.1700):否
7.openEuler-24.03-LTS-SP1(2.1700):否
8.openEuler-24.03-LTS-SP2(2.1700):否
9.openEuler-24.03-LTS-SP3(2.1700):否
10.openEuler-24.03-LTS-SP4(2.1700):否
原因说明：
1.master(2.2000):正常修复
2.openEuler-22.03-LTS-SP3(2.16):正常修复
3.openEuler-22.03-LTS-SP4(2.16):正常修复
4.openEuler-24.03-LTS(2.1700):正常修复
5.openEuler-24.03-LTS-Next(2.1700):正常修复
6.openEuler-24.03-LTS-SP1(2.1700):正常修复
7.openEuler-24.03-LTS-SP2(2.1700):正常修复
8.openEuler-20.03-LTS-SP4(2.16):不受影响-组件不存在
9.openEuler-24.03-LTS-SP3(2.1700):正常修复
10.openEuler-24.03-LTS-SP4(2.1700):正常修复