PULSE
FEED
ransommetaencryptor reclama a SRM Technologies · US · Technologyransommetaencryptor reclama a Over Easy Office · US · Retail & E-Commerceransommetaencryptor reclama a OmniPrint International · US · Manufacturingransommetaencryptor reclama a SEKISUI HOUSE, LTD · JP · Manufacturingransomshadowbyt3$ reclama a Chevron Corporation · US · Energy & Utilitiesransomshadowbyt3$ reclama a petstop · US · Retail & E-Commerceransomshadowbyt3$ reclama a University of British Columbia · CA · Educationransomshadowbyt3$ reclama a Gorcon Construction Inc · CA · Manufacturingransomshadowbyt3$ reclama a Glenmore Pharmacy & Medical Clinic · Healthcareransomvortex reclama a KOCH · DE · Energy & Utilitiesransomvortex reclama a CARRINGTON · GB · Financial Servicesransomaoqin reclama a Culinary Specialties · US · Retail & E-Commerceransombyod reclama a Michigan State University - New DL · US · Educationransombyod reclama a Texas HHSC - Final Warning & Sample · US · Government & Defenseransommetaencryptor reclama a SRM Technologies · US · Technologyransommetaencryptor reclama a Over Easy Office · US · Retail & E-Commerceransommetaencryptor reclama a OmniPrint International · US · Manufacturingransommetaencryptor reclama a SEKISUI HOUSE, LTD · JP · Manufacturingransomshadowbyt3$ reclama a Chevron Corporation · US · Energy & Utilitiesransomshadowbyt3$ reclama a petstop · US · Retail & E-Commerceransomshadowbyt3$ reclama a University of British Columbia · CA · Educationransomshadowbyt3$ reclama a Gorcon Construction Inc · CA · Manufacturingransomshadowbyt3$ reclama a Glenmore Pharmacy & Medical Clinic · Healthcareransomvortex reclama a KOCH · DE · Energy & Utilitiesransomvortex reclama a CARRINGTON · GB · Financial Servicesransomaoqin reclama a Culinary Specialties · US · Retail & E-Commerceransombyod reclama a Michigan State University - New DL · US · Educationransombyod reclama a Texas HHSC - Final Warning & Sample · US · Government & Defense
← Todos os CVEs
CVE Watch10 de nov. de 2026

CVE-2024-5535

Issue summary: Calling the OpenSSL API function SSL_select_next_proto with an empty supported client protocols buffer may cause a crash or m

CVSS

9.1

Crítica

EPSS

6.1%

p94

KEV

—

Exploit Today

28

0-100

Publicado: 27 de jun. de 2024 · Última mod.: 10 de nov. de 2026 · CWE-125

EPSS · 30d
5.6%EPSS · 30 dias6.1%
2026-10-182026-11-15
Descrição técnica

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.

Referências oficiais
CVEs relacionados
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2025-714705.5 MÉD
—
——0MicroQuickJS (mquickjs) before commit 99eed3f contains an out-of-bounds read vulnerability because JS_Call() raises exceptions during frame setup without updating ctx->sp and ctx->fp. Attackers can supply JavaScript that calls a non-function value, causing build_backtrace() to walk stale frame pointers and crash the engine for denial of service.23h
CVE-2026-1294805.3 MÉD
—
——0Assimp through 6.0.6 contains a heap out-of-bounds read vulnerability in MD2Importer::InternReadFile that allows attackers to read past the file buffer via an unvalidated stored frameSize header field. Attackers can supply a crafted .md2 file loaded with a non-zero keyframe selected to crash the application or leak adjacent heap memory into the imported mesh.1d
CVE-2026-1294786.1 MÉD
—
——0Assimp through 6.0.6 contains a heap out-of-bounds read vulnerability in glTFCommon::Util::ParseDataURI caused by storing the data offset in a signed char. Attackers can supply a crafted glTF file with a raw data URI whose segment starts beyond byte 127 to crash applications or leak adjacent heap memory.1d
CVE-2026-1294326.5 MÉD
10.6%
——3Ettercap through 0.8.5.1 contains a heap out-of-bounds read vulnerability in dissector_mountd() in src/dissectors/ec_mountd.c that validates RPC credential and directory lengths independently rather than against the packet end. Network-adjacent attackers can send a crafted MOUNT MNT call to read up to 100 bytes past the heap buffer, leaking memory to the console and logs.2d
CVE-2026-1294316.5 MÉD
14.4%
——4Ettercap through 0.8.5.1 contains a heap out-of-bounds read vulnerability in dissector_socks() in src/dissectors/ec_socks.c that allows network-adjacent attackers to read heap memory via unchecked SOCKS5 username/password lengths. Attackers can send a crafted SOCKS5 authentication packet observed by Ettercap to read up to 255 bytes past the heap buffer, disclosing memory printed and logged as captured credentials.2d
CVE-2026-646755.3 MÉD
42.0%
——13BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to versions 1.4.5 and 1.5.1, a single unauthenticated BACnet/IP UDP datagram (port 47808) triggers an out-of-bounds read in xy_color_decode() (src/bacnet/lighting.c), reachable pre-authentication through two default-registered service handlers: the UnconfirmedRequest WriteGroup service (0x0A) and Confirmed WriteProperty on a BACnetXYColor-typed property. This issue has been patched in versions 1.4.5, 1.5.1, and 1.6.0.3d