Bug Issue Usage Guide

• To change the issue status to 已验收, 已挂起, or 已取消, you need to perform the operation by commenting.
• If the issue is not associated with a milestone, either the issue creator or repository maintainer can change its status to one of the three states by commenting as shown in the table below.
• If the issue is associated with a milestone, refer to the table below.

Notice ❗

• When adding a milestone, if the current issue status is 已验收, 已挂起, or 已取消, manually change the status to 待办的.

Hi peulerosci, 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: Kernel, and any of the maintainers.

@xiexiuqi , @hanjun-guo , @zhengzengkai , @sanglipeng , @x56Jason , @CTC-XiboWang , @Frank_Sae , @Hongchen_Zhang , @JerryHZ , @LiYihang226 , @LiuYongQiang0816 , @Lostwayzxc , @SuperSix173 , @WangBoe2022 , @YGN-NDWD-Official , @Young1c , @allen-shi , @alvin-ling , @chenguangli , @chenke1978 , @chenwei_kernel , @chiqijun , @chris_zjh , @colyli , @duanqiangwen , @gaojuxin09 , @gasonchen , @georgeguo , @giree2 , @gouhao2022 , @guohaocs2c , @guzitao , @hanliyang , @haochengxie , @hellotcc , @hitmoon , @hjx_gitff , @htforge , @hu-chunzhi , @hunan4222 , @jentlestea , @jiaoff , @jimmy_hero , @juntianlinux , @kailiu42 , @kevinzhu1 , @kile2009 , @koishimind , @kongzizaixian , @kylin-mayukun , @lengchao , @leoliu-oc , @li-huisong , @linan888 , @liulongfang , @lixuefeng-loongson , @lujialin2 , @mao-hongbo , @maobibo , @markyuan4ta2 , @mingqian218472 , @newbeats , @qinirao , @shuaijiakun , @sming56_admin , @stavewu , @stkid , @wangxiongfeng , @whoisxxx , @wkfxxx , @woqidaideshi , @wsoydl , @xingmz , @xukuohai , @yeweihua999 , @yonghu_4dc5 , @youngersun , @yuehaibing_planb , @yunshenglin , @yuzenghui , @zhang-changzhong , @zhangyi089 , @zhenpengzheng , @zhujianwei001 , @zqiao216
以下的要求不是强制性的, 未按模板评论时对issue无任何影响
issue处理注意事项:
1. 当前issue受影响的分支提交pr时, 须在pr描述中填写当前issue编号进行关联, 否则无法关闭当前issue;
2. 模板内容需要填写完整, 无论是受影响或者不受影响都需要填写完整内容,未引入的分支不需要填写, 否则无法关闭当前issue;
3. 以下为模板中需要填写完整的内容, 请复制到评论区回复, 注: 内容的标题名称(影响性分析说明, 缺陷严重等级, 受影响版本排查(受影响/不受影响), 修复是否涉及abi变化(是/否))不能省略,省略后defect-manager将无法正常解析填写内容.
评论区可能使用到的指令说明:

影响性分析说明:

缺陷严重等级:(Critical/High/Moderate/Low)

缺陷根因说明:

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

1. openEuler-20.03-LTS-SP4:
2. openEuler-22.03-LTS-SP3:
3. openEuler-22.03-LTS-SP4:
4. openEuler-24.03-LTS:
5. openEuler-24.03-LTS-SP1:
6. openEuler-24.03-LTS-SP2:

abi变化(是/否):

1. openEuler-20.03-LTS-SP4:
2. openEuler-22.03-LTS-SP3:
3. openEuler-22.03-LTS-SP4:
4. openEuler-24.03-LTS:
5. openEuler-24.03-LTS-SP1:
6. openEuler-24.03-LTS-SP2:

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

影响性分析说明:
渗透测试，rpcb_register_inet6、rpcb_register_inet4函数中，调rpc_sockaddr2uaddr申请内存，没有检查返回值，导致空指针访问报错。
缺陷严重等级:(Critical/High/Moderate/Low)
Moderate
缺陷根因说明:
rpcb_register_inet6、rpcb_register_inet4函数中，调rpc_sockaddr2uaddr申请内存，没有检查返回值，导致空指针访问报错。
受影响版本排查(受影响/不受影响):

openEuler-20.03-LTS-SP4:不受影响
openEuler-22.03-LTS-SP3:受影响
openEuler-22.03-LTS-SP4:受影响
openEuler-24.03-LTS:受影响
openEuler-24.03-LTS-SP1:受影响
openEuler-24.03-LTS-SP2:受影响
abi变化(是/否):

openEuler-20.03-LTS-SP4:否
openEuler-22.03-LTS-SP3:否
openEuler-22.03-LTS-SP4:否
openEuler-24.03-LTS:否
openEuler-24.03-LTS-SP1:否
openEuler-24.03-LTS-SP2:否

@CTC-XiboWang 经过defect-manager解析，已分析的内容如下表所示:

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

@CTC-XiboWang
关闭issue前,需要将受影响的分支在合并pr时关联上当前issue编号: #6612
受影响分支: openEuler-22.03-LTS-SP3/openEuler-22.03-LTS-SP4/openEuler-24.03-LTS/openEuler-24.03-LTS-SP1/openEuler-24.03-LTS-SP2
具体操作参考: https://docs.gitcode.com/docs/help/home/org_project/pullrequests/pr-related-issue