166 matches found
CVE-2022-33679
CVE-2022-33679 One day based on https://googleprojectzero.blogspot.com/2022/10/rc4-is-still-considered-harmful.html Usage usage: CVE-2022-33079.py -h -ts -debug -dc-ip ip address target serverName Example...
CLSA-2026-1791803568 Fix CVE(s): CVE-2026-19445, CVE-2026-4786
SECURITY UPDATE: use-after-free in the ssl servername SNI callback - debian/patches/CVE-2026-19445.patch: take the SSLContext from the connection and hold references to it and to the callback while the callback runs, instead of using the borrowed pointer registered with OpenSSL, and unregister th...
CLSA-2026-1791493434 Fix CVE(s): CVE-2026-19445, CVE-2026-4786
SECURITY UPDATE: use-after-free in the ssl servername SNI callback CVE-2026-19445 - debian/patches/CVE-2026-19445.patch: look the SSLContext up from the SSL object instead of the borrowed pointer registered with OpenSSL, hold references to it and to the callback while it runs, and unregister the...
CLSA-2026-1791372827 Fix CVE(s): CVE-2026-19445, CVE-2026-4786
SECURITY UPDATE: use-after-free in the ssl servername SNI callback CVE-2026-19445 - debian/patches/CVE-2026-19445.patch: look the SSLContext up from the SSL object instead of the borrowed pointer registered with OpenSSL, hold references to it and to the callback while it runs, and unregister the...
CLSA-2026-1791967190 python2: Fix of CVE-2026-19445
CVE-2026-19445: fix a use-after-free in the SNI servername callback by taking the SSLContext from the live socket, with a strong reference, instead of the borrowed pointer registered on the SSLCTX, and by unregistering the callback in contextdealloc, so a context released after the callback has...
CLSA-2026-1791965784 python2: Fix of CVE-2026-19445
CVE-2026-19445: look up the SNI servername callback's SSLContext from the connection instead of the borrowed pointer registered with OpenSSL, and hold strong references to that context and to the callback while they are in use, so a callback that switches the socket to another context and drops...
CLSA-2026-1791530000 python3.11: Fix of 2 CVEs
CVE-2026-19445: ssl: resolve the SSLContext for the SNI servername callback from the connection instead of the borrowed SSLCTX argument, and unregister the callback in contextdealloc, so a context dropped after snicallback switched the connection is no longer used after it is freed -...
CLSA-2026-1791521362 python2: Fix of CVE-2026-19445
CVE-2026-19445: fix a use-after-free in the SNI servername callback servernamecallback in Modules/ssl.c...
CLSA-2026-1791433868 python3: Fix of CVE-2026-19445
CVE-2026-19445: ssl: do not call the servername callback through a released SSLContext use-after-free when the callback switches SSLSocket.context...
CLSA-2026-1791424578 python: Fix of CVE-2026-19445
CVE-2026-19445: fix use-after-free in the ssl servername SNI callback - the callback reached its SSLContext through a borrowed pointer registered with OpenSSL, so once the callback switched SSLSocket.context to another context and nothing else referenced the original one, the freed object was...
CLSA-2026-1791434822 python3: Fix of CVE-2026-19445
CVE-2026-19445: ssl: do not call the servername callback through a released SSLContext use-after-free when the callback switches SSLSocket.context...
CLSA-2026-1791425564 python: Fix of CVE-2026-19445
CVE-2026-19445: fix use-after-free in the ssl servername SNI callback - the callback reached its SSLContext through a borrowed pointer registered with OpenSSL, so once the callback switched SSLSocket.context to another context and nothing else referenced the original one, the freed object was...
CLSA-2026-1791425064 python: Fix of CVE-2026-19445
CVE-2026-19445: fix use-after-free in the ssl servername SNI callback - the callback reached its SSLContext through a borrowed pointer registered with OpenSSL, so once the callback switched SSLSocket.context to another context and nothing else referenced the original one, the freed object was...
Xray-core: Pinning a CA certificate via pinnedPeerCertSha256 can lead to the success of MITM attacks
Summary Pinning a CA certificate via pinnedPeerCertSha256 can lead to the success of MITM attacks in some cases. Details https://github.com/XTLS/Xray-core/blob/45cf2898ab12e97a55dd8f1f3d78d903340bdc9e/transport/internet/tls/config.goL333-L347 If r.Config.ServerName is empty, DNSName will be empty...
NPM: Nodemailer: Process-global DNS cache reuses TLS `servername` across transports, enabling cross-tenant SMTP credential disclosure
NPM: Nodemailer: Process-global DNS cache reuses TLS servername across transports, enabling cross-tenant SMTP credential disclosure vulnerability discovered by ? in WordPress Npm nodemailer versions = 5.0.0, 10.0.2...
Nodemailer: Process-global DNS cache reuses TLS `servername` across transports, enabling cross-tenant SMTP credential disclosure
Summary Nodemailer's process-global DNS cache is keyed only by host, but each cache entry also stores the caller-specific TLS servername. When two direct SMTPS transports use the same DNS host with different tls.servername values, the first transport's server name is returned to the second...
GHSA-6VJ9-MWQ6-2F5V Nodemailer: Process-global DNS cache reuses TLS `servername` across transports, enabling cross-tenant SMTP credential disclosure
Summary Nodemailer's process-global DNS cache is keyed only by host, but each cache entry also stores the caller-specific TLS servername. When two direct SMTPS transports use the same DNS host with different tls.servername values, the first transport's server name is returned to the second...
DEBIAN-CVE-2026-100701
Nodemailer versions 5.0.0 through 10.0.1 use a process-global DNS cache that is keyed only by the DNS host, while each cache entry also stores the caller-specific TLS servername. When two direct TLS/SMTPS transports secure: true resolve the same non-IP host with different tls.servername values, t...
CVE-2026-100701 Nodemailer 5.0.0 through 10.0.1 TLS servername Cache Confusion
Nodemailer versions 5.0.0 through 10.0.1 use a process-global DNS cache that is keyed only by the DNS host, while each cache entry also stores the caller-specific TLS servername. When two direct TLS/SMTPS transports secure: true resolve the same non-IP host with different tls.servername values, t...
EUVD-2026-87674
Nodemailer versions 5.0.0 through 10.0.1 use a process-global DNS cache that is keyed only by the DNS host, while each cache entry also stores the caller-specific TLS servername. When two direct TLS/SMTPS transports secure: true resolve the same non-IP host with different tls.servername values, t...