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

影响性分析说明:

openEuler评分: (评分和向量)

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

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

原因说明：
1.master(5.2.16):
2.openEuler-20.03-LTS-SP4(2.2.27):
3.openEuler-22.03-LTS-SP4(4.2.15):
4.openEuler-24.03-LTS-Next(4.2.15):
5.openEuler-24.03-LTS-SP1(4.2.15):
6.openEuler-24.03-LTS-SP3(4.2.15):
7.openEuler-24.03-LTS-SP4(4.2.15):

原因说明填写请参考下方表格(注意：版本是否受影响和版本的原因说明必须对应，例如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

Welcome To openEuler Community

Hey @openeuler-ci-bot , 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: sig-python-modules ,
and any of the maintainers: @shinwell_hu, @yangzhao_kl ,
and any of the committers: @cherry530, @randy1568, @starlet-dx .

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

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

openEuler评分: (评分和向量)
(请填写此字段)

受影响版本排查(受影响/不受影响):
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:(请填写此字段)

修复是否涉及abi变化(是/否)：
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:(请填写此字段)

原因说明：
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:(请填写此字段)

影响性分析说明:
该漏洞只影响5.2 before 5.2.17 and 6.0 before 6.0.8低于5.2的版本不受影响
openEuler评分: (评分和向量)
5.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
受影响版本排查(受影响/不受影响):
1.master(5.2.16):受影响
2.openEuler-20.03-LTS-SP4(2.2.27):不受影响
3.openEuler-22.03-LTS-SP4(4.2.15):不受影响
4.openEuler-24.03-LTS-Next(4.2.15):不受影响
5.openEuler-24.03-LTS-SP1(4.2.15):不受影响
6.openEuler-24.03-LTS-SP3(4.2.15):不受影响
7.openEuler-24.03-LTS-SP4(4.2.15):不受影响

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

原因说明：
1.master(5.2.16):正常修复
2.openEuler-20.03-LTS-SP4(2.2.27):不受影响-漏洞代码不存在
3.openEuler-22.03-LTS-SP4(4.2.15):不受影响-漏洞代码不存在
4.openEuler-24.03-LTS-Next(4.2.15):不受影响-漏洞代码不存在
5.openEuler-24.03-LTS-SP1(4.2.15):不受影响-漏洞代码不存在
6.openEuler-24.03-LTS-SP3(4.2.15):不受影响-漏洞代码不存在
7.openEuler-24.03-LTS-SP4(4.2.15):不受影响-漏洞代码不存在

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

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

影响性分析说明:
An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8.django.utils.translation.check_for_language() is subject to a potential denial-of-service attack when given many distinct, very long language codes, which are retained as keys in an in-memory cache and consume process memory. Such codes reach the function through the django.views.i18n.set_language() view, which is not routed by default. The consumed memory is bounded, since request data is limited by the DATA_UPLOAD_MAX_MEMORY_SIZE setting (default 2.5 MB) and the cache holds a fixed maximum number of entries.Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected.Django would like to thank Jaeyoung Jang for reporting this issue.
openEuler评分: (评分和向量)
5.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
受影响版本排查(受影响/不受影响)：
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:受影响

修复是否涉及abi变化(是/否)：
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:否

原因说明：
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:暂不修复-暂无解决方案或补丁

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

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

影响性分析说明:
An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8.django.utils.translation.check_for_language() is subject to a potential denial-of-service attack when given many distinct, very long language codes, which are retained as keys in an in-memory cache and consume process memory. Such codes reach the function through the django.views.i18n.set_language() view, which is not routed by default. The consumed memory is bounded, since request data is limited by the DATA_UPLOAD_MAX_MEMORY_SIZE setting (default 2.5 MB) and the cache holds a fixed maximum number of entries.Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected.Django would like to thank Jaeyoung Jang for reporting this issue.
openEuler评分: (评分和向量)
6.9
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
受影响版本排查(受影响/不受影响)：
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:受影响

修复是否涉及abi变化(是/否)：
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:否

原因说明：
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:暂不修复-暂无解决方案或补丁

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

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

影响性分析说明:
An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8.django.utils.translation.check_for_language() is subject to a potential denial-of-service attack when given many distinct, very long language codes, which are retained as keys in an in-memory cache and consume process memory. Such codes reach the function through the django.views.i18n.set_language() view, which is not routed by default. The consumed memory is bounded, since request data is limited by the DATA_UPLOAD_MAX_MEMORY_SIZE setting (default 2.5 MB) and the cache holds a fixed maximum number of entries.Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected.Django would like to thank Jaeyoung Jang for reporting this issue.

openEuler评分: (评分和向量)
6.9
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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

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

原因说明：
1.master(5.2.17):正常修复
2.openEuler-20.03-LTS-SP4(2.2.27):暂不修复-暂无解决方案或补丁
3.openEuler-22.03-LTS-SP4(4.2.15):正常修复
4.openEuler-24.03-LTS-Next(4.2.15):正常修复
5.openEuler-24.03-LTS-SP1(4.2.15):正常修复
6.openEuler-24.03-LTS-SP3(4.2.15):正常修复
7.openEuler-24.03-LTS-SP4(4.2.15):正常修复

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

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