Low-level invalid GF(2^m) parameters lead to OOB memory access
36811
27 January 2026
27 January 2026
CLOSED
LOW
4.3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
CVE-2024-9143
|
Brocade Security Advisory ID |
BSA-2026-2762 |
|
Component |
OpenSSL |
|
CWE |
CWE-125: CWE-125 Out-of-bounds Read CWE-787: CWE-787 Out-of-bounds Write |
|
|
|
Summary
Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the field polynomial can lead to out-of-bounds memory reads or writes.
Impact summary: Out of bound memory writes can lead to an application crash or even a possibility of a remote code execution, however, in all the protocols involving Elliptic Curve Cryptography that we're aware of, either only "named curves" are supported, or, if explicit curve parameters are supported, they
specify an X9.62 encoding of binary (GF(2^m)) curves that can't represent problematic input values. Thus the likelihood of existence of a vulnerable application is low.
In particular, the X9.62 encoding is used for ECC keys in X.509 certificates, so problematic inputs cannot occur in the context of processing X.509 certificates.?? Any problematic use-cases would have to be using an "exotic" curve encoding.
The affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(),
and various supporting BN_GF2m_*() functions.
Applications working with "exotic" explicit binary (GF(2^m)) curve parameters, that make it possible to represent invalid field polynomials with a zero constant term, via the above or similar APIs, may terminate abruptly as a result of reading or writing outside of array bounds.
Products Affected
- No Brocade products are affected
Products Not Affected
- Brocade Fabric OS
[VEX Justification: Vulnerable_code_cannot_be_contolled_by_adversary] - Brocade SANnav
[VEX Justification: Vulnerable_code_not_in_execute_path] - Brocade ASCG
[VEX Justification: Vulnerable_code_not_in_execute_path]
Solution
- While not exploitable, a security update is included in Brocade FabricOS 10.0.0
- While not exploitable, a security update is included in Brocade SANnav 2.4.0b and 3.0.0
Revision History
|
Version |
Change |
Date |
|
1.0 |
Initial Publication |
January 27, 2026 |
Disclaimer
THIS DOCUMENT IS PROVIDED ON AN AS-IS BASIS SOLELY FOR INFORMATIONAL PURPOSES AND DOES NOT IMPLY ANY KIND OF GUARANTY OR WARRANTY, INCLUDING THE WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. YOUR USE OF THE INFORMATION CONTAINED HEREIN IS AT YOUR OWN RISK. ALL INFORMATION PROVIDED HEREIN IS BASED ON BROCADE'S CURRENT KNOWLEDGE AND UNDERSTANDING OF THE VULNERABILITY AND IMPACT TO BROCADE HARDWARE AND SOFTWARE PRODUCTS. BROCADE RESERVES THE RIGHT TO CHANGE OR UPDATE THIS DOCUMENT AT ANY TIME.