Apache Log4j Core versions 2.0-beta9 through 2.25.2 contain a vulnerability in the Socket Appender where TLS hostname verification is not properly performed, even if configured to do so. This flaw can allow a man-in-the-middle attacker to intercept or redirect log traffic if they can present a trusted certificate and intercept network traffic. The issue is addressed in version 2.25.3. Users can alternatively mitigate by restricting the trust root to limit trusted certificates.
GoSign Desktop through 2.4.1 disables TLS certificate validation when configured to use a proxy server. This can be problematic if the GoSign Desktop user selects an arbitrary proxy server without consideration of whether outbound HTTPS connections from the proxy server to Internet servers succeed even for untrusted or invalid server certificates. In this scenario (which is outside of the product's design objectives), integrity protection could be bypassed. In typical cases of a proxy server for outbound HTTPS traffic from an enterprise, those connections would not succeed. (Admittedly, the usual expectation is that a client application is configured to trust an enterprise CA and does not set SSL_VERIFY_NONE.) Also, it is of course unsafe to place ~/.gosign in the home directory of an untrusted user and then have other users execute downloaded files.
KubeVirt's virt-api component has an authentication bypass vulnerability in the Kubernetes aggregation layer due to improper validation of the Common Name (CN) in client TLS certificates. This flaw allows an attacker with a valid front-end proxy certificate and network access to the virt-api service to impersonate the Kubernetes API server aggregator, bypassing RBAC controls. Exploitation requires possession of a trusted certificate and network access within the cluster, limiting the attack surface. Successful exploitation could enable a pod-level attacker to escalate privileges and manipulate virtual machine workloads, impacting availability. The issue is fixed in KubeVirt versions 1.5.3, 1.6.1, and 1.7.0-rc.0.
Akka.NET is a .NET port of the Akka project from the Scala / Java community. In all versions of Akka.Remote from v1.2.0 to v1.5.51, TLS could be enabled via our `akka.remote.dot-netty.tcp` transport and this would correctly enforce private key validation on the server-side of inbound connections. Akka.Remote, however, never asked the outbound-connecting client to present ITS certificate - therefore it's possible for untrusted parties to connect to a private key'd Akka.NET cluster and begin communicating with it without any certificate. The issue here is that for certificate-based authentication to work properly, ensuring that all members of the Akka.Remote network are secured with the same private key, Akka.Remote needed to implement mutual TLS. This was not the case before Akka.NET v1.5.52. Those who run Akka.NET inside a private network that they fully control or who were never using TLS in the first place are now affected by the bug. However, those who use TLS to secure their networks must upgrade to Akka.NET V1.5.52 or later. One patch forces "fail fast" semantics if TLS is enabled but the private key is missing or invalid. Previous versions would only check that once connection attempts occurred. The second patch, a critical fix, enforces mutual TLS (mTLS) by default, so both parties must be keyed using the same certificate. As a workaround, avoid exposing the application publicly to avoid the vulnerability having a practical impact on one's application. However, upgrading to version 1.5.52 is still recommended by the maintainers.
Vasion Print (formerly PrinterLogic) Virtual Appliance Host versions prior to 25.1.102 and Application prior to 25.1.1413 (Windows client deployments) contain a hardcoded private key for the PrinterLogic Certificate Authority (CA) and a hardcoded password in product configuration files. The Windows client ships the CA certificate and its associated private key (and other sensitive settings such as a configured password) directly in shipped configuration files (for example clientsettings.dat and defaults.ini). An attacker who obtains these files can impersonate the CA, sign arbitrary certificates trusted by the Windows client, intercept or decrypt TLS-protected communications, and otherwise perform man-in-the-middle or impersonation attacks against the product's network communications. This vulnerability has been identified by the vendor as: V-2022-001 — Configuration File Contains CA & Private Key.
A vulnerability exists in the Kubernetes C# client where the certificate validation logic accepts properly constructed certificates from any Certificate Authority (CA) without properly verifying the trust chain. This flaw allows a malicious actor to present a forged certificate and potentially intercept or manipulate communication with the Kubernetes API server, leading to possible man-in-the-middle attacks and API impersonation.
A security update for python-requests addresses a vulnerability (CVE-2024-47081) where a maliciously crafted URL combined with a trusted environment could cause credentials to be retrieved from a netrc file for the wrong hostname or machine. This update also fixes issues related to certificate caching in sslcontext and includes other improvements.
Icinga 2 is a monitoring system which checks the availability of network resources, notifies users of outages, and generates performance data for reporting. Prior to versions 2.12.12, 2.13.12, and 2.14.6, the VerifyCertificate() function can be tricked into incorrectly treating certificates as valid. This allows an attacker to send a malicious certificate request that is then treated as a renewal of an already existing certificate, resulting in the attacker obtaining a valid certificate that can be used to impersonate trusted nodes. This only occurs when Icinga 2 is built with OpenSSL older than version 1.1.0. This issue has been patched in versions 2.12.12, 2.13.12, and 2.14.6.
CVE-2025-1014 is a vulnerability in mozjs52 where the certificate length was not properly checked when added to a certificate store. The issue was mitigated by the fact that only trusted data was processed in practice. This vulnerability was fixed in Firefox 135, Firefox ESR 128.7, Thunderbird 128.7, and Thunderbird 135. The CVSS v3.1 score is 8.8, indicating a high severity impact with network attack vector, low attack complexity, no privileges required, user interaction required, and high impact on confidentiality, integrity, and availability.
Icinga is a monitoring system which checks the availability of network resources, notifies users of outages, and generates performance data for reporting. The TLS certificate validation in all Icinga 2 versions starting from 2.4.0 was flawed, allowing an attacker to impersonate both trusted cluster nodes as well as any API users that use TLS client certificates for authentication (ApiUser objects with the client_cn attribute set). This vulnerability has been fixed in v2.14.3, v2.13.10, v2.12.11, and v2.11.12.
A fraudulent Certificate Authority (CA) issued HTTPS certificates that are trusted by Network Security Services (NSS) using the Builtin Object Token. This security advisory from Red Hat addresses this issue by updating NSS to mark such certificates as untrusted. The update affects all uses of these certificates, including SSL, S/MIME, and code signing, but only for applications using the NSS Builtin Object Token. Applications using NSS but not the Builtin Object Token are not affected by this change. Users must upgrade NSS and restart affected applications for the update to take effect.