Smartkeyss

Name of the Vulnerable Software and Affected Versions: urllib3 versions prior to 1.26.19 urllib3 versions prior to 2.2.2 Description: The issue is related to the handling of the `Proxy-Authorization` header in urllib3, a Python HTTP client library. When using urllib3's proxy support with `ProxyManager`, the `Proxy-Authorization` header is only sent to the configured proxy. However, when sending HTTP requests without using urllib3's proxy support, it's possible to accidentally configure the `Proxy-Authorization` header, which won't have any effect but can still be sent on cross-origin redirects. This can potentially allow a remote attacker to obtain sensitive information. The severity of this issue is considered low for almost all users, as it requires specific conditions to be exploited: setting the `Proxy-Authorization` header without using urllib3's built-in proxy support, not disabling HTTP redirects, and either not using an HTTPS origin server or redirecting to a malicious origin. Recommendations: Update to version 1.26.19 or version 2.2.2 to resolve the issue. For versions prior to 1.26.19, use the `Proxy-Authorization` header with urllib3's `ProxyManager` as a mitigation. For versions prior to 2.2.2, disable HTTP redirects using `redirects=False` when sending requests as a mitigation. Alternatively, do not use the `Proxy-Authorization` header as a mitigation for versions prior to 1.26.19 and 2.2.2.

**Name of the Vulnerable Software and Affected Versions** NLTK versions 3.8.1 and earlier **Description** The issue is related to the nltk.download() function in the NLTK library, which can lead to remote code execution when untrusted packages containing pickled Python code are downloaded. This particularly affects the averaged perceptron tagger and punkt packages. The exploitation of this issue may allow a remote attacker to execute arbitrary code. **Recommendations** For NLTK versions 3.8.1 and earlier, as a temporary workaround, consider disabling the integrated data package download functionality until a patch is available. Restrict access to untrusted packages to minimize the risk of exploitation. Avoid using the nltk.download() function for packages that may contain pickled Python code until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** libcurl (affected versions not specified) **Description** The issue is related to the implementation of TLS protocols in libcurl, where the server certificate is not checked when connecting to a host specified as an IP address, when built to use mbedTLS. This affects all uses of TLS protocols, including HTTPS, FTPS, IMAPS, POPS3, SMTPS, etc. The vulnerability can be exploited by a remote attacker to conduct spoofing attacks. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** PuTTY versions 0.68 through 0.80 FileZilla versions 3.24.1 through 3.66.5 WinSCP versions 5.9.5 through 6.3.2 TortoiseGit versions 2.4.0.2 through 2.15.0 TortoiseSVN versions 1.10.0 through 1.14.6 **Description** The issue is related to biased ECDSA nonce generation in PuTTY, allowing an attacker to recover a user's NIST P-521 secret key via a quick attack in approximately 60 signatures. This is especially important in scenarios where an adversary can read messages signed by PuTTY or Pageant, such as when messages are stored in a public Git service that supports SSH for commit signing. The vulnerability can be exploited to compromise private keys, potentially leading to unauthorized access to servers and services. In some cases, this could enable supply-chain attacks on software maintained in Git. **Recommendations** For PuTTY versions 0.68 through 0.80, update to version 0.81 or later to fix the security issue. For FileZilla versions 3.24.1 through 3.66.5, update to version 3.67.0 or later. For WinSCP versions 5.9.5 through 6.3.2, update to version 6.3.3 or later. For TortoiseGit versions 2.4.0.2 through 2.15.0, update to version 2.15.0.1 or later. For TortoiseSVN versions 1.10.0 through 1.14.6, apply the available workaround or wait for a patch.

**Name of the Vulnerable Software and Affected Versions** Google Chrome versions prior to 120.0.6099.224 Microsoft Edge (affected versions not specified) **Description** An out-of-bounds write exists in the V8 JavaScript engine, which is the component responsible for executing JavaScript code. This flaw allows a remote attacker to potentially exploit heap corruption—a condition where memory allocation in the heap is corrupted—via a specially crafted HTML page. Successful exploitation could lead to arbitrary code execution, bypassing the Chrome sandbox, or causing a denial of service. Real-world incidents have been reported where this issue was exploited in the wild. **Recommendations** Update Google Chrome to version 120.0.6099.224 or later. At the moment, there is no information about a newer version that contains a fix for this vulnerability for Microsoft Edge.

**Name of the Vulnerable Software and Affected Versions** Google Chrome versions prior to 116.0.5845.187 libwebp versions prior to 1.3.2 **Description** A heap buffer overflow exists in the libwebp library used for encoding and decoding images in WebP format. A remote attacker can perform an out-of-bounds memory write by inducing the library to process a maliciously crafted HTML page or WebP image. This memory corruption occurs during the image decoding process and can lead to an application crash or the execution of arbitrary code. The issue has been actively exploited in the wild, including as part of zero-click exploits. Due to the widespread integration of libwebp, the flaw affects millions of applications and billions of devices globally, including major browsers and communication apps. **Recommendations** Update Google Chrome to version 116.0.5845.187 or later. Update libwebp to version 1.3.2 or later.

**Name of the Vulnerable Software and Affected Versions** OpenSSH versions 8.5p1 through 9.2p1-2+deb12u3 **Description** An unauthenticated remote attacker can exploit a signal handler race condition in the OpenSSH server (sshd). The issue occurs when a client fails to authenticate within the `LoginGraceTime` period (defaulting to 120 seconds, or 600 seconds in older versions), triggering the `SIGALRM` handler asynchronously. This handler calls functions that are not async-signal-safe, such as `syslog()`, which can lead to the reuse of previously freed memory. This flaw allows a remote attacker to execute arbitrary code with root privileges. The issue is a regression of a previously reported flaw and affects sshd in its default configuration. **Recommendations** Upgrade OpenSSH packages to version 1:9.2p1-2+deb12u3 or newer. As a temporary mitigation, restrict access to the `sshd` service to minimize the risk of exploitation.