Welcome To openEuler Community

Hey @fundawang , thanks for your contribution to the community.

Bot Usage Manual

I'm the Bot here serving you. You can find the instructions on how to interact with me at Here . That means you can comment below every pull request or issue to trigger Bot Commands.

Contact Guide

If you have any questions, please contact the SIG: Base-service ,
and any of the maintainers: @dillon_chen, @licihua, @overweight, @shenyangyang, @xujing99, @zhujianwei001 ,
and any of the committers: @hubin1305, @jiayi0118, @luckky7, @lvying6, @znzju .

issue处理注意事项:
1. 提交正常修复分支的修复PR时,必须关联当前issue,否则无法关闭当前issue;
2. 模板内容需要填写完整, 无论是受影响或者不受影响都需要填写完整内容;
3. 以下为模板中需要填写完整的内容, 请复制到评论区回复;
注: 内容的关键词(影响性分析说明, openEuler评分, 受影响版本排查(受影响/不受影响), 修复是否涉及abi变化(是/否), 原因说明)不能省略,省略后cve-manager将无法正常解析填写内容.

影响性分析说明:

openEuler评分: (评分和向量)

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

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

原因说明：
1.master(3.4.4):
2.openEuler-20.03-LTS-SP4(3.1.3):
3.openEuler-22.03-LTS-SP4(3.2.5):
4.openEuler-24.03-LTS-Next(3.4.4):
5.openEuler-24.03-LTS-SP1(3.2.7):
6.openEuler-24.03-LTS-SP3(3.2.7):
7.openEuler-24.03-LTS-SP4(3.2.7):

原因说明填写请参考下方表格(注意：版本是否受影响和版本的原因说明必须对应，例如master版本分支受影响，那原因说明只能是受影响对应的原因之一!)：

issue处理具体操作请参考:
https://atomgit.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
pr关联issue具体操作请参考:
https://docs.atomgit.com/docs/help/home/org_project/pullrequests/pr-related-issue

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

@fundawang CVE信息从NVD同步失败, 请稍后重试, 或者数据源不存在.

影响性分析说明: rsync: sender source-tree parent-component symlink race -> out-of-tree disclosure

A local/non-daemon sender opened each transferred file's content by path (O_NOFOLLOW on the leaf only). A parent component an unprivileged user raced from a real directory to a symlink->outside after the file-list scan was then followed, so a higher-authority sender -- a root nightly backup, or a victim copying an attacker's tree -- read and copied a file from OUTSIDE the source tree into a destination the attacker can read (information disclosure of files the attacker could not otherwise read).

Fix: for default symlink handling, open the content through secure_relative_open(O_RDONLY|O_NOFOLLOW) anchored at the transfer root, so a parent that escaped the tree is refused; the symlink-following modes (-L, --copy-unsafe-links, -k) still follow, and --insecure-links restores the legacy open. The daemon sender was already module_dir-anchored.

Test: symlink-race-source.

Affected: rsync 3.4.3 and earlier; fixed in 3.5.0. (Precise introduced-in ranges being finalised.)

openEuler评分: 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

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

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

原因说明：
1.master(3.4.4): 正常修复
2.openEuler-20.03-LTS-SP4(3.1.3): 正常修复
3.openEuler-22.03-LTS-SP4(3.2.5): 正常修复
4.openEuler-24.03-LTS-Next(3.4.4): 正常修复
5.openEuler-24.03-LTS-SP1(3.2.7): 正常修复
6.openEuler-24.03-LTS-SP3(3.2.7): 正常修复
7.openEuler-24.03-LTS-SP4(3.2.7): 正常修复

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

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

经过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未合入)

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

原因说明：
1.master:正常修复
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未合入)

经过 cve-manager 解析 openEuler评分 已改变 需要您及时进行审核,以便maintainer进行后续操作.

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

@gitee-cmd, @zhujianwei001, @luoyukai, @kylincuilei, @tanjingguo, @tangjie, @mailofzxf, @zeng-wei2000, @Sam-Luo The CVE score needs to be reviewed (the review instruction /approve or /reject means agreement and rejection).

@fundawang ,请给出NVD评分和openEuler评分不一致的理由

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

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

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

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