Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2024-5535

openssl: SSL_select_next_proto buffer overread

Overview

Published
27 Jun 2024
Modified
10 Nov 2026
Critical CVE
2 Registry packages
100 OS packages
21 Linux distributions
Yes Fix available

Description

Issue summary: Calling the OpenSSL API function SSL_select_next_proto with an
empty supported client protocols buffer may cause a crash or memory contents to
be sent to the peer.

Impact summary: A buffer overread can have a range of potential consequences
such as unexpected application beahviour or a crash. In particular this issue
could result in up to 255 bytes of arbitrary private data from memory being sent
to the peer leading to a loss of confidentiality. However, only applications
that directly call the SSL_select_next_proto function with a 0 length list of
supported client protocols are affected by this issue. This would normally never
be a valid scenario and is typically not under attacker control but may occur by
accident in the case of a configuration or programming error in the calling
application.

The OpenSSL API function SSL_select_next_proto is typically used by TLS
applications that support ALPN (Application Layer Protocol Negotiation) or NPN
(Next Protocol Negotiation). NPN is older, was never standardised and
is deprecated in favour of ALPN. We believe that ALPN is significantly more
widely deployed than NPN. The SSL_select_next_proto function accepts a list of
protocols from the server and a list of protocols from the client and returns
the first protocol that appears in the server list that also appears in the
client list. In the case of no overlap between the two lists it returns the
first item in the client list. In either case it will signal whether an overlap
between the two lists was found. In the case where SSL_select_next_proto is
called with a zero length client list it fails to notice this condition and
returns the memory immediately following the client list pointer (and reports
that there was no overlap in the lists).

This function is typically called from a server side application callback for
ALPN or a client side application callback for NPN. In the case of ALPN the list
of protocols supplied by the client is guaranteed by libssl to never be zero in
length. The list of server protocols comes from the application and should never
normally be expected to be of zero length. In this case if the
SSL_select_next_proto function has been called as expected (with the list
supplied by the client passed in the client/client_len parameters), then the
application will not be vulnerable to this issue. If the application has
accidentally been configured with a zero length server list, and has
accidentally passed that zero length server list in the client/client_len
parameters, and has additionally failed to correctly handle a "no overlap"
response (which would normally result in a handshake failure in ALPN) then it
will be vulnerable to this problem.

In the case of NPN, the protocol permits the client to opportunistically select
a protocol when there is no overlap. OpenSSL returns the first client protocol
in the no overlap case in support of this. The list of client protocols comes
from the application and should never normally be expected to be of zero length.
However if the SSL_select_next_proto function is accidentally called with a
client_len of 0 then an invalid memory pointer will be returned instead. If the
application uses this output as the opportunistic protocol then the loss of
confidentiality will occur.

This issue has been assessed as Low severity because applications are most
likely to be vulnerable if they are using NPN instead of ALPN - but NPN is not
widely used. It also requires an application configuration or programming error.
Finally, this issue would not typically be under attacker control making active
exploitation unlikely.

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

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 releases when they
become available.

Source: OX vulnerability database

Severity

9.1 · CRITICAL

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Weakness: CWE-125

Affected packages · 2

Packages affected by CVE-2024-5535
EcosystemPackageVulnerableFixed in
Julia Openresty_jll <1.27.1+0 1.27.1+0
Julia OpenSSL_jll <3.0.15+0 3.0.15+0

Open a package to see all its vulnerabilities.

Operating systems · 106 fixes

Azure Linux 1 release · 1 package

fixed 1
openssl
Azure Linux fixes for CVE-2024-5535
ReleasePackageFixed in
3.0 openssl 0:3.3.0-2.azl3

Oracle Linux 2 releases · 6 packages

fixed 9
mecab mingw32-openssl openssl mecab-ipadic mysql openssl-fips-provider
Oracle Linux fixes for CVE-2024-5535
ReleasePackageFixed in
8 mecab +1 0.996-2.module+el8.10.0+90521+d5cc5c65
8 mingw32-openssl +1 1.0.2k-4.el8_10
8 openssl +3 1:1.1.1k-14.el8_6
8 mecab-ipadic +1 2.7.0.20070801-17.0.1.module+el8.10.0+90521+d5cc5c65
8 openssl +4 2:1.1.1k-14.ksplice1.el8_6
8 mysql +6 8.0.41-1.module+el8.10.0+90521+d5cc5c65

3 more rows

Photon OS 2 releases · 1 package

fixed 2
openssl
Photon OS fixes for CVE-2024-5535
ReleasePackageFixed in
4.0 openssl +4 3.0.14-2.ph4
5.0 openssl +5 3.0.14-3.ph5

Red Hat 4 releases · 13 packages

affected 3 eol 1 fixed 18
aavmf rh-mysql80-mysql jbcs-httpd24-mod-http2 jbcs-httpd24-httpd openssl jbcs-httpd24-openssl +7
Red Hat fixes for CVE-2024-5535
ReleasePackageFixed inAdvisory
7 aavmf +2 affected —
7 rh-mysql80-mysql +10 eol —
7 jbcs-httpd24-mod-http2 0:2.0.29-3.el7jbcs RHSA-2025:3452
7 jbcs-httpd24-httpd +6 0:2.4.62-5.el7jbcs RHSA-2025:3452
7 openssl +4 1:1.0.2k-26.el7_9.2 RHSA-2026:58563
7 jbcs-httpd24-openssl +4 1:1.1.1k-19.el7jbcs RHSA-2025:3452

16 more rows

SUSE Linux Enterprise 4 releases · 4 packages

fixed 12
libopenssl-1-0-0-devel libopenssl-1-1-devel libopenssl-3-devel openssl-3-livepatches
SUSE Linux Enterprise fixes for CVE-2024-5535
ReleasePackageFixed inAdvisory
12.5 libopenssl-1-0-0-devel +7 1.0.2p-3.95.1 SUSE-SU-2024:2989-1
12.5 libopenssl-1-1-devel +6 1.1.1d-2.110.2 SUSE-SU-2024:2953-1
15.4 libopenssl-1-0-0-devel +4 1.0.2p-150000.3.94.1 SUSE-SU-2024:3119-1
15.4 libopenssl-1-1-devel +6 1.1.1l-150400.7.72.1 SUSE-SU-2024:2927-1
15.4 libopenssl-3-devel +2 3.0.8-150400.4.60.1 SUSE-SU-2024:2931-1
15.5 libopenssl-1-0-0-devel +4 1.0.2p-150000.3.94.1 SUSE-SU-2024:3119-1

6 more rows

SUSE Linux Enterprise Micro 6 releases · 5 packages

fixed 10
libopenssl-1-1-devel libopenssl3 libpulp-tools libopenssl-3-devel jitterentropy-devel
SUSE Linux Enterprise Micro fixes for CVE-2024-5535
ReleasePackageFixed inAdvisory
5.1 libopenssl-1-1-devel +3 1.1.1d-150200.11.94.1 SUSE-SU-2024:2909-1
5.2 libopenssl-1-1-devel +3 1.1.1d-150200.11.94.1 SUSE-SU-2024:2909-1
5.3 libopenssl-1-1-devel +3 1.1.1l-150400.7.72.1 SUSE-SU-2024:2927-1
5.3 libopenssl3 3.0.8-150400.4.60.1 SUSE-SU-2024:2931-1
5.4 libopenssl-1-1-devel +3 1.1.1l-150400.7.72.1 SUSE-SU-2024:2927-1
5.4 libopenssl3 3.0.8-150400.4.60.1 SUSE-SU-2024:2931-1

4 more rows

alma 3 releases · 6 packages

fixed 8
mingw32-openssl openssl mecab-devel mecab mecab-ipadic mysql
alma fixes for CVE-2024-5535
ReleasePackageFixed in
8 mingw32-openssl +1 1.0.2k-4.el8_10
8 openssl +3 1:1.1.1k-14.el8_6
8 (mysql:8.0) mecab-devel 0.996-2.module_el8.10.0+3965+b415b607
8 (mysql:8.0) mecab 0.996-2.module_el8.6.0+3340+d764b636
8 (mysql:8.0) mecab-ipadic +1 2.7.0.20070801-17.module_el8.10.0+3965+b415b607
8 (mysql:8.0) mysql +6 8.0.41-1.module_el8.10.0+3965+b415b607

2 more rows

alpine 4 releases · 1 package

fixed 4
openssl
alpine fixes for CVE-2024-5535
ReleasePackageFixed in
3.22 openssl 3.3.1-r1
3.23 openssl 3.3.1-r1
3.24 openssl 3.3.1-r1
edge openssl 3.3.1-r1

amazon linux 1 release · 1 package

fixed 1
openssl
amazon linux fixes for CVE-2024-5535
ReleasePackageFixed in
2023 openssl +8 1:3.0.8-1.amzn2023.0.14

chainguard 1 release · 2 packages

not affected 1 fixed 1
openssl-provider-fips openssl
chainguard fixes for CVE-2024-5535
ReleasePackageFixed in
openssl-provider-fips +1 not affected
openssl 3.3.1-r3

debian 4 releases · 1 package

fixed 4
openssl
debian fixes for CVE-2024-5535
ReleasePackageFixed in
11 openssl 1.1.1w-0+deb11u2
12 openssl 3.0.15-1~deb12u1
13 openssl 3.3.2-1
14 openssl 3.3.2-1

echo 1 release · 3 packages

fixed 3
openssl openssl-3-0-9 openssl-3-1-0
echo fixes for CVE-2024-5535
ReleasePackageFixed in
openssl 3.0.15-1~deb12u1
openssl-3-0-9 3.0.9+e1
openssl-3-1-0 3.1.0+e1

openSUSE 1 release · 2 packages

fixed 2
libopenssl-1-1-devel libopenssl-3-devel
openSUSE fixes for CVE-2024-5535
ReleasePackageFixed inAdvisory
Tumbleweed libopenssl-1-1-devel +5 1.1.1w-11.1 openSUSE-SU-2024:14219-1
Tumbleweed libopenssl-3-devel +9 3.1.4-11.1 openSUSE-SU-2024:14220-1

openSUSE Leap Micro 1 release · 1 package

fixed 1
libopenssl-1-1-devel
openSUSE Leap Micro fixes for CVE-2024-5535
ReleasePackageFixed inAdvisory
5.5 libopenssl-1-1-devel +3 1.1.1l-150500.17.34.1 SUSE-SU-2024:2891-1

rocky 3 releases · 4 packages

fixed 6
openssl mecab mecab-ipadic mysql
rocky fixes for CVE-2024-5535
ReleasePackageFixed in
8 openssl +3 1:1.1.1k-14.el8_10
8 (mysql:8.0) mecab +1 0.996-2.module+el8.10.0+1676+9b4b6e24
8 (mysql:8.0) mecab-ipadic +1 2.7.0.20070801-17.module+el8.10.0+1937+28fbbc83
8 (mysql:8.0) mysql +6 8.0.41-1.module+el8.10.0+1937+28fbbc83.0.1
9 openssl +3 1:3.2.2-6.el9_5.1
9 mysql +3 8.0.41-2.el9_5

root.io alpine 1 release · 1 package

fixed 1
rootio-openssl
root.io alpine fixes for CVE-2024-5535
ReleasePackageFixed in
3.23 rootio-openssl 3.3.1-r1

root.io debian 2 releases · 1 package

fixed 2
rootio-openssl
root.io debian fixes for CVE-2024-5535
ReleasePackageFixed in
11 rootio-openssl 1.1.1w-0+deb11u2
12 rootio-openssl 3.0.15-1~deb12u1

seal Red Hat 2 releases · 1 package

fixed 4
openssl
seal Red Hat fixes for CVE-2024-5535
ReleasePackageFixed in
7 openssl +1 1:1.0.2k-25.el7_9+sp999
7 openssl +1 1:1.0.2k-26.el7_9+sp999
8 openssl +1 1:1.1.1k-14.el8_6+sp999
8 openssl +1 1:1.1.1k-6.el8_5+sp999

seal debian 1 release · 1 package

fixed 2
openssl
seal debian fixes for CVE-2024-5535
ReleasePackageFixed in
openssl +1 1.1.1w-0+deb11u2+sp999
openssl +1 3.0.16-1~deb12u1+sp999

ubuntu 6 releases · 3 packages

fixed 9
openssl1-0 openssl edk2
ubuntu fixes for CVE-2024-5535
ReleasePackageFixed in
18.04-ESM openssl1-0 1.0.2n-1ubuntu5.13+esm6
18.04-ESM openssl 1.1.1-1ubuntu2.1~18.04.23+esm10
20.04 openssl 1.1.1f-1ubuntu2.23
20.04-ESM openssl 1.1.1f-1ubuntu2.23
22.04 edk2 2022.02-3ubuntu0.22.04.4
22.04 openssl 3.0.2-0ubuntu1.17

3 more rows

wolfi 1 release · 1 package

fixed 1
openssl
wolfi fixes for CVE-2024-5535
ReleasePackageFixed in
openssl 3.3.1-r3

References

Show all 97 references

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.