CVE-2026-71883— Native AES密文解析器泄露原始AES密钥
一分钟漏洞结论
影响对象
Legion of the Bouncy Castle Inc. BC-LTS-JAVA
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
在 Java 长期支持版本（LTS）中，Bouncy Castle 在 2.73.13 版本之前存在一个漏洞：AES-CBC、CCM、CFB、CTR、GCM 和 GCM-SIV 的一次性原生包密码（native packet ciphers）在使用 JNI 的 ReleaseByteArrayElements 方法时，以模式 0（mode 0）释放调用者传入的密钥（key）、初始化向量（IV）以及附加认证数据（additional authenticated data）数组。模式 0 会将原生内存副本写回 Java
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-71883 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
Native AES packet cipher returns the raw AES key on an alias
来源: CVE Program / CVE List V5
Vulnerability Description
In Bouncy Castle for Java LTS before 2.73.13, the one-shot native packet ciphers for AES-CBC, CCM, CFB, CTR, GCM and GCM-SIV released the caller's key, IV and additional authenticated data arrays with JNI's ReleaseByteArrayElements in mode 0, which commits the native copy back into the Java array. Those arrays are read-only to the native code, and on a JVM that returns a copy rather than a pin the copy still holds the input bytes as they were read. The output buffer is taken through a separate critical region and committed first, so where an application passed the same Java array as both an input and the destination - encrypting in place over KeyParameter.getKey(), for example - the later mode-0 release of the key wrote the unchanged key bytes over the ciphertext that had just been produced. The call still returned the correct output length, so an application encrypting in place over its own key array was handed the raw AES key where it expected ciphertext, with nothing in the API to indicate it, and would transmit or store the key in place of the message. The read-only input arrays are now released with JNI_ABORT, freeing the native copy without copying it back, and mode 0 is reserved for arrays the native code wrote. The pure-Java packet ciphers and the streaming native modes are not affected. Bouncy Castle for Java (bcprov) is not affected, as it ships no native implementations.
来源: CVE Program / CVE List V5
CVSS Information
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/U:Amber
来源: CVE Program / CVE List V5
Vulnerability Type
信息暴露
来源: CVE Program / CVE List V5
受影响产品
| 厂商 | 产品 | 影响版本 | CPE | 订阅 |
|---|---|---|---|---|
| Legion of the Bouncy Castle Inc. | BC-LTS-JAVA | 2.73.4 ~ 2.73.13 | - |
|
二、漏洞 CVE-2026-71883 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-71883 的情报信息
请登录查看更多情报信息。
CVE-2026-71883 其他参考 (1)
同批安全公告 · Legion of the Bouncy Castle Inc. · 2026-10-03 · 共 9 条
| CVE-2026-71885 | 9.2 CRITICAL | MLS X.509凭证未绑定到LeafNode签名密钥 |
| CVE-2026-71888 | 8.7 HIGH | CMS 认证数据暴露攻击者插入的authAttrs |
| CVE-2026-71889 | 8.7 HIGH | PKIXCertPathReviewer X.509名称约束绕过漏洞 |
| CVE-2026-85515 | 8.2 HIGH | OpenPGP消息截断未报告，绕过SEIPDv1完整性检查 |
| CVE-2026-71887 | 8.2 HIGH | OpenPGP 签名子键无交叉认证漏洞 |
| CVE-2026-71886 | 8.2 HIGH | OpenPGP 子键无证书认证漏洞 |
| CVE-2026-71892 | 6.9 MEDIUM | RFC 9709 HKDF派生密钥未执行CMS密钥传输接收方密钥大小验证 |
| CVE-2026-97873 | 5.3 MEDIUM | JCA原始提供程序未限制PBES1和PKCS#12迭代次数 |
IV. Related Vulnerabilities
V. Comments for CVE-2026-71883
暂无评论