OpenSSL Security Advisory

--=-CZSYzskjcKGtixEO9UGs
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

OpenSSL Security Advisory [16th October 2024]
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Low-level invalid GF(2^m) parameters lead to OOB memory access (CVE-2024-91=
43)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D

Severity: Low

Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrus=
ted
explicit values for the field polynomial can lead to out-of-bounds memory r=
eads
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 protocol=
s
involving Elliptic Curve Cryptography that we're aware of, either only "nam=
ed
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 certificate=
s,
so problematic inputs cannot occur in the context of processing X.509
certificates.=C2=A0 Any problematic use-cases would have to be using an "ex=
otic"
curve encoding.

The affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_par=
ams(),
and various supporting BN_GF2m_*() functions.

Applications working with "exotic" explicit binary (GF(2^m)) curve paramete=
rs,
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.=C2=A0 Remote code exe=
cution
cannot easily be ruled out.

The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.

OpenSSL 3.3, 3.2, 3.1, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.

OpenSSL 3.3 users should upgrade to OpenSSL 3.3.3 once it is released.

OpenSSL 3.2 users should upgrade to OpenSSL 3.2.4 once it is released.

OpenSSL 3.1 users should upgrade to OpenSSL 3.1.8 once it is released.

OpenSSL 3.0 users should upgrade to OpenSSL 3.0.16 once it is released.

OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1zb once it is released
(premium support customers only).

OpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zl once it is released
(premium support customers only).

Due to the low severity of this issue we are not issuing new releases of
OpenSSL at this time. The fix will be included in the next release of each
branch, once it becomes available. The fix is also available in commit
c0d3e4d3 (for 3.3), commit bc7e04d7 (for 3.2), commit fdf67233 (for 3.1)
and commit 72ae83ad (for 3.0) in the OpenSSL git repository. It is availabl=
e
to premium support customers in commit 8efc0cba (for 1.1.1) and in commit
9d576994 (for 1.0.2).

This issue was reported on 16th September 2024 by Google OSS-Fuzz-Gen.
The fix was developed by Viktor Dukhovni.

General Advisory Notes
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

URL for this Security Advisory:
https://openssl-library.org/news/secadv/20241016.txt

Note: the online version of the advisory may be updated with additional det=
ails
over time.

For details of OpenSSL severity classifications please see:
https://openssl-library.org/policies/general/security-policy/

--=20
You received this message because you are subscribed to the Google Groups "=
openssl-announce" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to [email protected].
To view this discussion on the web visit https://groups.google.com/a/openss=
l.org/d/msgid/openssl-announce/7c9240d98ed0c87cc19f38867d15480fe0fea7e1.cam=
el%40openssl.org.

--=-CZSYzskjcKGtixEO9UGs
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----

iQJGBAABCAAwFiEE3HAyZir4heL0fyQ/UnRmohynnm0FAmcP8aoSHHRvbWFzQG9w
ZW5zc2wub3JnAAoJEFJ0ZqIcp55tLD4P/32lDpFQ9GBQHaGyinQsGCSAxyYETv4b
nwK2Mc3dzHJb4jcrDqHb2WcC2viSV9JgnVSt/dWwGbTqbANmI4kahxeYF/OnLN4W
yDl+Gmeap2mN2aSwq4X2xGjHhnJu7MawAyESmhOpNeGUUHucBui6Qckfa/uKrOyA
ngImiTaWbUm0Z1SbXAelIAwBPJddBHls/ph6dmvVqoYbCqh43qNQUMGcpP9Mc0vV
vcztQGOqnn+dsBCuZ7aa7y/78Igj3b6ElNU5mjmLmTOlOaZfxic/IJ/vVF48EV6e
EmVIeISVwIHzms/RM2VGuCF3us6orJHET70SNxGlC9+mBac0KwSkViZ95+HE3mKD
udyBV/6slijh/t+yGZD6S66FWSb/SHmuqu0jgvylyAEXGT2CJtOnC82bQX0++EeS
XwNENI28UKE5G3MAR9OhLuVOtDq7NMmme6BADIniZ2HTnC3I6xiz/0GUUrsYTTaj
uXRMSt+w0KY6w/DdkvH3d6X2e4ODBzkY5fbhHF5ArIu+N6LbsB2Fd9XPfzbHJoQD
YTZ9egkFtd6GvWRbKM5OhPwyjLDMj9BDoA/vD3tRNVuUwvvNIwd4pLVREXyoV/jZ
7k+rXXnb9u2TQ3CKHQcbiLDwN+jj314CWxhJ15EXmwmDtDn6vVyxRrI5NgnOAYEt
TO5k7QX+TBE+
=ux4t
-----END PGP SIGNATURE-----

--=-CZSYzskjcKGtixEO9UGs--