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. You can self-configure the PR merge rules for this repository. For more details, please refer to Here.
Contact Guide
If you have any questions, please contact the SIG: sig-security-facility ,
and any of the maintainers: @mailofzxf, @robertosassu, @zhujianwei001 ,
and any of the committers: @gcw_n2PeTU3z, @zcfsite .
issue处理注意事项:
1. 提交正常修复分支的修复PR时,必须关联当前issue,否则无法关闭当前issue;
2. 模板内容需要填写完整, 无论是受影响或者不受影响都需要填写完整内容;
3. 以下为模板中需要填写完整的内容, 请复制到评论区回复;
注: 内容的关键词(影响性分析说明, openEuler评分, 受影响版本排查(受影响/不受影响), 修复是否涉及abi变化(是/否), 原因说明)不能省略,省略后cve-manager将无法正常解析填写内容.
影响性分析说明:
openEuler评分: (评分和向量)
受影响版本排查(受影响/不受影响):
1.master(3.5.8):
2.openEuler-20.03-LTS-SP4(1.1.1f):
3.openEuler-22.03-LTS-SP4(1.1.1wa):
4.openEuler-24.03-LTS-Next(3.5.6):
5.openEuler-24.03-LTS-SP1(3.0.12):
6.openEuler-24.03-LTS-SP3(3.0.12):
7.openEuler-24.03-LTS-SP4(3.5.6):
修复是否涉及abi变化(是/否)：
1.master(3.5.8):
2.openEuler-20.03-LTS-SP4(1.1.1f):
3.openEuler-22.03-LTS-SP4(1.1.1wa):
4.openEuler-24.03-LTS-Next(3.5.6):
5.openEuler-24.03-LTS-SP1(3.0.12):
6.openEuler-24.03-LTS-SP3(3.0.12):
7.openEuler-24.03-LTS-SP4(3.5.6):
原因说明：
1.master(3.5.8):
2.openEuler-20.03-LTS-SP4(1.1.1f):
3.openEuler-22.03-LTS-SP4(1.1.1wa):
4.openEuler-24.03-LTS-Next(3.5.6):
5.openEuler-24.03-LTS-SP1(3.0.12):
6.openEuler-24.03-LTS-SP3(3.0.12):
7.openEuler-24.03-LTS-SP4(3.5.6):
原因说明填写请参考下方表格(注意：版本是否受影响和版本的原因说明必须对应，例如master版本分支受影响，那原因说明只能是受影响对应的原因之一!)：
分支状态 |
原因说明 | 使用场景 |
|---|---|---|
| 受影响 | 正常修复 | 受影响且需要修复（包含升级版本修复）的漏洞； 受影响且已经修复的漏洞（历史修复PR也需要关联issue）； 若因特殊原因无法修复，应修改原因说明为【不修复-特殊原因】，并在安委会备案相关情况。 |
| 受影响 | 暂不修复-漏洞仍在分析中 | 已关注到相关漏洞，正在处理，未明确漏洞影响和修复方案。 |
| 受影响 | 暂不修复-暂无解决方案或补丁 | 当前没有可用的修复或补救措施。【影响性分析】中应包含有关为什么没有修复或补救措施的详细说明、上游相关PR等。 |
| 受影响 | 不修复-超出修复范围 | 没有漏洞的修复计划。当版本停维、软件包宣布生命周期终止或弃用使用。 |
| 受影响 | 不修复-特殊原因导致不再修复 | 如存在其他特殊情况不修复相关漏洞，或评估后无法升级修复，应在openEuler社区安全委员会例会进行说明备案。 【影响性分析】中应包含不发布修复的详细说明、特殊情况还应有安委会会议纪要。 |
| 不受影响 | 不受影响-组件不存在 | 软件不受影响，因为易受攻击的组件不在产品中。 |
| 不受影响 | 不受影响-已有内置的内联控制或缓解措施 | 内置的内联控制或缓解措施可防止攻击者利用漏洞 |
| 不受影响 | 不受影响-漏洞代码不能被攻击者触发 | 易受攻击的组件存在，并且该组件包含易受攻击的代码。但是，易受攻击的代码的使用方式使得攻击者无法进行任何预期的攻击。 |
| 不受影响 | 不受影响-漏洞代码不在执行路径 | 易受影响的代码在执行过程中不可访问，包括产品的非预期状态。产品不使用也不执行的组件。 |
| 不受影响 | 不受影响-漏洞代码不存在 | 产品不受影响，因为漏洞背后的代码在产品中不存在。与component_not_present不同的是，有问题的组件存在，但由于某种原因（例如安全的编译器选项）使漏洞的特定代码不存在于组件中。 |
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
| 参考网址 | 关联pr | 状态 | 补丁链接 |
|---|---|---|---|
| https://www.opencve.io/cve/CVE-2026-84784 | |||
| https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2026-84784 | |||
| https://security-tracker.debian.org/tracker/CVE-2026-84784 | |||
| http://www.cnnvd.org.cn/web/vulnerability/queryLds.tag?qcvCnnvdid=CVE-2026-84784 | |||
| https://nvd.nist.gov/vuln/detail/CVE-2026-84784 | |||
| https://ubuntu.com/security/CVE-2026-84784 | None | None | https://discourse.ubuntu.com/c/project |
说明：补丁链接仅供初步排查参考，实际可用性请人工再次确认，补丁下载验证可使用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同步失败, 请稍后重试, 或者数据源不存在.
/branches openEuler-20.03-LTS-SP4 openEuler-22.03-LTS-SP4 openEuler-24.03-LTS-SP1 openEuler-24.03-LTS-SP3 /name hugel /email 2712504175@qq.com
【任务 #296 · openEuler-20.03-LTS-SP4】CVE-2026-84784
是否受影响：不受影响
CVE-2026-84784 的自有补丁经 Step 4 源码影响性分析判为 NOT_APPLICABLE，漏洞代码不存在于本版本（openssl 1.1.1f）源码中，无需修复。
各分支状态：
- openEuler-20.03-LTS-SP4（1.1.1f）：不受影响（ABI 变化：否）
是否有修复补丁：有
上游社区补丁：https://github.com/openssl/openssl/commit/9a30fe0fba195c14e5b87bf93c0d0fdb70373806.patch
补丁适配情况：无适配。该补丁对本分支源码判为 NOT_APPLICABLE（漏洞代码不存在），无需落地适配，也不涉及前置补丁。
是否提交 PR：无 PR。本分支经分析不受影响，无需提交修复 PR。
──────── 复制以下内容回填 issue ────────
受影响版本排查(受影响/不受影响)：
1.openEuler-20.03-LTS-SP4(1.1.1f): 不受影响
ABI 变化：否
原因说明：
1.不受影响-漏洞代码不存在
────────────────────────────────────────
任务已识别：根据事实清单为 issue #296（openssl，openEuler-22.03-LTS-SP4 分支，CVE-2026-84784）生成中文评论。事实已核对（Step 4 影响性分析判定 NOT_APPLICABLE：1.1.1wa 源码树无 QUIC 栈，quic_channel.c 及全部漏洞符号缺失），按要求直接输出评论如下：
【任务 #296 · openEuler-22.03-LTS-SP4】CVE-2026-84784
是否受影响：不受影响
CVE-2026-84784 为 OpenSSL QUIC 栈的内存耗尽拒绝服务漏洞：恶意对端绕过连接 ID 数量限制检查，向本地 QUIC 栈洪水式发送 NEW_CONNECTION_ID 帧，无界积压控制帧队列导致内存 DoS。经 Step 4 源码影响性分析对 openssl-1.1.1wa 全源码树实际验证：源码中不存在 ssl/quic/ 目录及 quic_channel.c，漏洞相关符号（QUIC_CHANNEL、cur_retire_prior_to、ch_enqueue_retire_conn_id、ossl_quic_cfq_add_frame 等）整体缺失——QUIC 栈自 OpenSSL 3.2 才引入，1.1.1wa 不含该漏洞代码路径，故本版本不受影响，无需修复。
分支状态：
- openEuler-22.03-LTS-SP4（openssl 1.1.1wa）：不受影响（漏洞代码不存在，补丁判为 NOT_APPLICABLE），ABI 变化：否
是否有修复补丁：有，上游社区补丁：
https://github.com/openssl/openssl/commit/9a30fe0fba195c14e5b87bf93c0d0fdb70373806.patch
补丁适配情况：无需适配。该补丁仅修改 QUIC 栈文件 ssl/quic/quic_channel.c，经源码影响性分析判为 NOT_APPLICABLE（漏洞代码不存在于本版本源码，核心符号整体缺失、无适配基底），故未进行任何适配，亦无前置补丁。
是否提交 PR：本次未提交 PR（本分支不受影响，无需修复）。
──────── 复制以下内容回填 issue ────────
受影响版本排查(受影响/不受影响)：
1.openEuler-22.03-LTS-SP4(1.1.1wa): 不受影响
ABI 变化：否
原因说明：
1.不受影响-漏洞代码不存在
────────────────────────────────────────
【任务 #296 · openEuler-24.03-LTS-SP3】CVE-2026-84784
是否受影响： 不受影响
CVE-2026-84784 的自有补丁经 Step 4 源码影响性分析判为 NOT_APPLICABLE，漏洞代码不存在于本版本源码中，无需修复。
分支状态：
- openEuler-24.03-LTS-SP3（3.0.12）：不受影响（漏洞代码不存在，补丁 NOT_APPLICABLE）
是否有修复补丁： 有
上游社区补丁：https://github.com/openssl/openssl/commit/9a30fe0fba195c14e5b87bf93c0d0fdb70373806.patch
补丁适配情况： 无需适配
该补丁经源码影响性分析判定为 NOT_APPLICABLE，漏洞代码不存在于 openEuler-24.03-LTS-SP3 的 openssl 3.0.12 源码，因此未进行补丁适配，也无前置补丁。
是否提交 PR： 无
本分支不受影响，无需修复，因此未提交 PR。
──────── 复制以下内容回填 issue ────────
受影响版本排查(受影响/不受影响)：
1.openEuler-24.03-LTS-SP3(3.0.12): 不受影响
ABI 变化：否
原因说明：
1.不受影响-漏洞代码不存在
────────────────────────────────────────
任务已识别：根据事实清单为 issue #296（openssl，openEuler-24.03-LTS-SP1 分支）生成 CVE-2026-84784 的分析评论。事实清单显示该 CVE 判定为不受影响（补丁 NOT_APPLICABLE），无适配、无 PR、无流水线失败。以下为评论内容：
【任务 #296 · openEuler-24.03-LTS-SP1】CVE-2026-84784
1. 是否受影响
结论：不受影响。
CVE-2026-84784 的自有补丁经 Step 4 源码影响性分析判为 NOT_APPLICABLE，漏洞代码不存在于本版本源码，无需修复。
分支状态：
- openEuler-24.03-LTS-SP1（openssl 3.0.12）：不受影响（漏洞代码不存在，补丁 NOT_APPLICABLE）
2. 是否有修复补丁
上游社区已有修复补丁：
https://github.com/openssl/openssl/commit/9a30fe0fba195c14e5b87bf93c0d0fdb70373806.patch
3. 补丁适配情况
无适配。该补丁经源码影响性分析判为 NOT_APPLICABLE（漏洞代码不存在于本版本源码），无需在 openEuler-24.03-LTS-SP1 分支进行任何适配。
4. 是否提交 PR
无 PR。本分支不受影响，无需提交修复 PR。
──────── 复制以下内容回填 issue ────────
受影响版本排查(受影响/不受影响)：
1.openEuler-24.03-LTS-SP1(3.0.12): 不受影响
ABI 变化：否
原因说明：
1.不受影响-漏洞代码不存在
────────────────────────────────────────
影响性分析说明：Issue summary: A malicious remote peer may flood the local QUICstack with NEW_CONNECTION_ID frames by avoiding a limit check onhow many connection IDs the remote QUIC stack can use.Impact summary: The local QUIC stack sends a RETIRE_CONN_ID framefor every NEW_CONNECTION_ID frame it receives. The RETIRE_CONN_IDframe is dispatched via the Control Frame Queue (CFQ). If the remotepeer also withholds ACKs, then it can force the local stackto allocate ~400MB (depending on ACK delay).CWE: CWE-770: Allocation of Resources Without Limits or ThrottlingDescription: RFC 9000 sections 5.1.1 and 5.1.2 [1] describe the mechanismby which a remote peer can notify the local QUIC stack to change thedestination connection ID (a.k.a. CID) the local stack uses toidentify the connection at the remote peer. Each CID is associatedwith a sequence number. The sequence number is transmittedin NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames to identify the CIDwhich is being either associated with a connection or retired.The remote peer sends a NEW_CONNECTION_ID frame to let the local stack knowa new CID is being associated with an existing connection. TheNEW_CONNECTION_ID frame carries the new CID, its sequence number, and theretire-prior-to number. The retire-prior-to identifies existingCIDs that are to be retired. The local QUIC stack must send aRETIRE_CONNECTION_ID for every destination CID whose sequence numberis less than retire-prior-to. The CID becomes retired after thelocal stack receives an ACK for its RETIRE_CONNECTION_ID frame.Although the OpenSSL QUIC stack supports at most one destination CIDfor every connection, it can be tricked into processing more thanone RETIRE_CONNECTION_ID frame per connection. The OpenSSL QUICstack currently retires the destination CID as soon as it receivesthe NEW_CONNECTION_ID, while in fact the destination CID mustbe retired after an ACK for the RETIRE_CONNECTION_ID frame is received.Correcting the flawed logic also fixes the backlog growth.[1] https://datatracker.ietf.org/doc/html/rfc9000#name-issuing-connection-idsFIPS impact: noThe FIPS module is not affected as the QUIC implementation is outside ofthe OpenSSL FIPS module boundary.
openEuler评分：
7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
受影响版本排查(受影响/不受影响)：
1.master(3.5.8):受影响
2.openEuler-20.03-LTS-SP4(1.1.1f):不受影响
3.openEuler-22.03-LTS-SP4(1.1.1wa):不受影响
4.openEuler-24.03-LTS-Next(3.5.6):受影响
5.openEuler-24.03-LTS-SP1(3.0.12):不受影响
6.openEuler-24.03-LTS-SP3(3.0.12):不受影响
7.openEuler-24.03-LTS-SP4(3.5.6):受影响
修复是否涉及abi变化(是/否)：
1.master(3.5.8):否
2.openEuler-20.03-LTS-SP4(1.1.1f):否
3.openEuler-22.03-LTS-SP4(1.1.1wa):否
4.openEuler-24.03-LTS-Next(3.5.6):否
5.openEuler-24.03-LTS-SP1(3.0.12):否
6.openEuler-24.03-LTS-SP3(3.0.12):否
7.openEuler-24.03-LTS-SP4(3.5.6):否
原因说明：
1.master(3.5.8):正常修复
2.openEuler-20.03-LTS-SP4(1.1.1f):不受影响-漏洞代码不存在
3.openEuler-22.03-LTS-SP4(1.1.1wa):不受影响-漏洞代码不存在
4.openEuler-24.03-LTS-Next(3.5.6):正常修复
5.openEuler-24.03-LTS-SP1(3.0.12):不受影响-漏洞代码不存在
6.openEuler-24.03-LTS-SP3(3.0.12):不受影响-漏洞代码不存在
7.openEuler-24.03-LTS-SP4(3.5.6):正常修复
@robertosassu 经过 cve-manager 解析, 已分析的内容如下表所示:
| 状态 | 分析项目 | 内容 |
|---|---|---|
| 已分析 | 1.影响性分析说明 | Issue summary: A malicious remote peer may flood the local QUICstack with NEW_CONNECTION_ID frames by avoiding a limit check onhow many connection IDs the remote QUIC stack can use.Impact summary: The local QUIC stack sends a RETIRE_CONN_ID framefor every NEW_CONNECTION_ID frame it receives. The RETIRE_CONN_IDframe is dispatched via the Control Frame Queue (CFQ). If the remotepeer also withholds ACKs, then it can force the local stackto allocate ~400MB (depending on ACK delay).CWE: CWE-770: Allocation of Resources Without Limits or ThrottlingDescription: RFC 9000 sections 5.1.1 and 5.1.2 [1] describe the mechanismby which a remote peer can notify the local QUIC stack to change thedestination connection ID (a.k.a. CID) the local stack uses toidentify the connection at the remote peer. Each CID is associatedwith a sequence number. The sequence number is transmittedin NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames to identify the CIDwhich is being either associated with a connection or retired.The remote peer sends a NEW_CONNECTION_ID frame to let the local stack knowa new CID is being associated with an existing connection. TheNEW_CONNECTION_ID frame carries the new CID, its sequence number, and theretire-prior-to number. The retire-prior-to identifies existingCIDs that are to be retired. The local QUIC stack must send aRETIRE_CONNECTION_ID for every destination CID whose sequence numberis less than retire-prior-to. The CID becomes retired after thelocal stack receives an ACK for its RETIRE_CONNECTION_ID frame.Although the OpenSSL QUIC stack supports at most one destination CIDfor every connection, it can be tricked into processing more thanone RETIRE_CONNECTION_ID frame per connection. The OpenSSL QUICstack currently retires the destination CID as soon as it receivesthe NEW_CONNECTION_ID, while in fact the destination CID mustbe retired after an ACK for the RETIRE_CONNECTION_ID frame is received.Correcting the flawed logic also fixes the backlog growth.[1] https://datatracker.ietf.org/doc/html/rfc9000#name-issuing-connection-idsFIPS impact: noThe FIPS module is not affected as the QUIC implementation is outside ofthe OpenSSL FIPS module boundary. |
| 已分析 | 2.openEulerScore | 7.5 |
| 已分析 | 3.openEulerVector | AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| 已分析 | 4.受影响版本排查 | master:受影响,openEuler-20.03-LTS-SP4:不受影响,openEuler-22.03-LTS-SP4:不受影响,openEuler-24.03-LTS-Next:受影响,openEuler-24.03-LTS-SP1:不受影响,openEuler-24.03-LTS-SP3:不受影响,openEuler-24.03-LTS-SP4:受影响 |
| 已分析 | 5.是否涉及abi变化 | master:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS-SP4:否,openEuler-24.03-LTS-Next:否,openEuler-24.03-LTS-SP1:否,openEuler-24.03-LTS-SP3:否,openEuler-24.03-LTS-SP4:否 |
| 已分析 | 6.原因说明 | master:正常修复,openEuler-20.03-LTS-SP4:不受影响-漏洞代码不存在,openEuler-22.03-LTS-SP4:不受影响-漏洞代码不存在,openEuler-24.03-LTS-Next:正常修复,openEuler-24.03-LTS-SP1:不受影响-漏洞代码不存在,openEuler-24.03-LTS-SP3:不受影响-漏洞代码不存在,openEuler-24.03-LTS-SP4:正常修复 |
请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.
经过cve-manager解析，(所有PR均已合入)
经过cve-manager解析，(所有PR均已合入)
一、漏洞信息
漏洞编号：CVE-2026-84784
漏洞归属组件：openssl
漏洞归属的版本：3.0.12
CVSS评分：
BaseScore：7.5 High
Vector：CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
漏洞简述：
Issue summary: A malicious remote peer may flood the local QUICstack with NEW_CONNECTION_ID frames by avoiding a limit check onhow many connection IDs the remote QUIC stack can use.Impact summary: The local QUIC stack sends a RETIRE_CONN_ID framefor every NEW_CONNECTION_ID frame it receives. The RETIRE_CONN_IDframe is dispatched via the Control Frame Queue (CFQ). If the remotepeer also withholds ACKs, then it can force the local stackto allocate ~400MB (depending on ACK delay).CWE: CWE-770: Allocation of Resources Without Limits or ThrottlingDescription: RFC 9000 sections 5.1.1 and 5.1.2 [1] describe the mechanismby which a remote peer can notify the local QUIC stack to change thedestination connection ID (a.k.a. CID) the local stack uses toidentify the connection at the remote peer. Each CID is associatedwith a sequence number. The sequence number is transmittedin NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames to identify the CIDwhich is being either associated with a connection or retired.The remote peer sends a NEW_CONNECTION_ID frame to let the local stack knowa new CID is being associated with an existing connection. TheNEW_CONNECTION_ID frame carries the new CID, its sequence number, and theretire-prior-to number. The retire-prior-to identifies existingCIDs that are to be retired. The local QUIC stack must send aRETIRE_CONNECTION_ID for every destination CID whose sequence numberis less than retire-prior-to. The CID becomes retired after thelocal stack receives an ACK for its RETIRE_CONNECTION_ID frame.Although the OpenSSL QUIC stack supports at most one destination CIDfor every connection, it can be tricked into processing more thanone RETIRE_CONNECTION_ID frame per connection. The OpenSSL QUICstack currently retires the destination CID as soon as it receivesthe NEW_CONNECTION_ID, while in fact the destination CID mustbe retired after an ACK for the RETIRE_CONNECTION_ID frame is received.Correcting the flawed logic also fixes the backlog growth.[1] https://datatracker.ietf.org/doc/html/rfc9000#name-issuing-connection-idsFIPS impact: noThe FIPS module is not affected as the QUIC implementation is outside ofthe OpenSSL FIPS module boundary.
漏洞公开时间：2026-09-30 00:17:12
漏洞创建时间：2026-09-29 23:27:31
漏洞详情参考链接：
https://nvd.nist.gov/vuln/detail/CVE-2026-84784
更多参考(点击展开)
无
漏洞分析指导链接：
https://atomgit.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
漏洞数据来源:
其他
漏洞补丁信息：
详情(点击展开)
无
二、漏洞分析结构反馈
影响性分析说明：
Issue summary: A malicious remote peer may flood the local QUICstack with NEW_CONNECTION_ID frames by avoiding a limit check onhow many connection IDs the remote QUIC stack can use.Impact summary: The local QUIC stack sends a RETIRE_CONN_ID framefor every NEW_CONNECTION_ID frame it receives. The RETIRE_CONN_IDframe is dispatched via the Control Frame Queue (CFQ). If the remotepeer also withholds ACKs, then it can force the local stackto allocate ~400MB (depending on ACK delay).CWE: CWE-770: Allocation of Resources Without Limits or ThrottlingDescription: RFC 9000 sections 5.1.1 and 5.1.2 [1] describe the mechanismby which a remote peer can notify the local QUIC stack to change thedestination connection ID (a.k.a. CID) the local stack uses toidentify the connection at the remote peer. Each CID is associatedwith a sequence number. The sequence number is transmittedin NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames to identify the CIDwhich is being either associated with a connection or retired.The remote peer sends a NEW_CONNECTION_ID frame to let the local stack knowa new CID is being associated with an existing connection. TheNEW_CONNECTION_ID frame carries the new CID, its sequence number, and theretire-prior-to number. The retire-prior-to identifies existingCIDs that are to be retired. The local QUIC stack must send aRETIRE_CONNECTION_ID for every destination CID whose sequence numberis less than retire-prior-to. The CID becomes retired after thelocal stack receives an ACK for its RETIRE_CONNECTION_ID frame.Although the OpenSSL QUIC stack supports at most one destination CIDfor every connection, it can be tricked into processing more thanone RETIRE_CONNECTION_ID frame per connection. The OpenSSL QUICstack currently retires the destination CID as soon as it receivesthe NEW_CONNECTION_ID, while in fact the destination CID mustbe retired after an ACK for the RETIRE_CONNECTION_ID frame is received.Correcting the flawed logic also fixes the backlog growth.[1] https://datatracker.ietf.org/doc/html/rfc9000#name-issuing-connection-idsFIPS impact: noThe FIPS module is not affected as the QUIC implementation is outside ofthe OpenSSL FIPS module boundary.
openEuler评分：
7.5
Vector：CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
受影响版本排查(受影响/不受影响)：
1.master(3.5.9):受影响
2.openEuler-20.03-LTS-SP4(1.1.1f):不受影响
3.openEuler-22.03-LTS-SP4(1.1.1wa):不受影响
4.openEuler-24.03-LTS-Next(3.5.6):受影响
5.openEuler-24.03-LTS-SP1(3.0.12):不受影响
6.openEuler-24.03-LTS-SP3(3.0.12):不受影响
7.openEuler-24.03-LTS-SP4(3.5.6):受影响
修复是否涉及abi变化(是/否)：
1.master(3.5.9):否
2.openEuler-20.03-LTS-SP4(1.1.1f):否
3.openEuler-22.03-LTS-SP4(1.1.1wa):否
4.openEuler-24.03-LTS-Next(3.5.6):否
5.openEuler-24.03-LTS-SP1(3.0.12):否
6.openEuler-24.03-LTS-SP3(3.0.12):否
7.openEuler-24.03-LTS-SP4(3.5.6):否
原因说明：
1.master(3.5.9):正常修复
2.openEuler-20.03-LTS-SP4(1.1.1f):不受影响-漏洞代码不存在
3.openEuler-22.03-LTS-SP4(1.1.1wa):不受影响-漏洞代码不存在
4.openEuler-24.03-LTS-Next(3.5.6):正常修复
5.openEuler-24.03-LTS-SP1(3.0.12):不受影响-漏洞代码不存在
6.openEuler-24.03-LTS-SP3(3.0.12):不受影响-漏洞代码不存在
7.openEuler-24.03-LTS-SP4(3.5.6):正常修复