CVE-2025-2230

A flaw exists in the Windows login flow where an AuthContext token can be exploited for replay attacks and authentication bypass...

CVE-2025-2230 Philips Intellispace Cardiovascular (ISCV) Improper Authentication

A flaw exists in the Windows login flow where an AuthContext token can be exploited for replay attacks and authentication bypass...

CVE-2025-2230 Philips Intellispace Cardiovascular (ISCV) Improper Authentication

A flaw exists in the Windows login flow where an AuthContext token can be exploited for replay attacks and authentication bypass...

CVE-2025-2230

A CVE for Philips ISCV (CVE-2025-2230) describes a Windows logon flow flaw where an AuthContext token can be replayed to bypass authentication. The token is generated from the username, current timestamp, and a fixed AES-128 key shared across installations, enabling high-impact confidentiality an...

Linux Distros Unpatched Vulnerability : CVE-2015-8466

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - Swift3 before 1.9 allows remote attackers to conduct replay attacks via an Authorization request that lacks a Date header. CVE-2015-8466 Note that Nessus relies...

Linux Distros Unpatched Vulnerability : CVE-2015-8140

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - The ntpq protocol in NTP before 4.2.8p7 allows remote attackers to conduct replay attacks by sniffing the network. CVE-2015-8140 Note that Nessus relies on the...

CVE-2025-0752

A flaw was found in OpenShift Service Mesh 2.6.3 and 2.5.6. Rate-limiter avoidance, access-control bypass, CPU and memory exhaustion, and replay attacks may be possible due to improper HTTP header sanitization in Envoy...

CVE-2025-0752

A flaw was found in OpenShift Service Mesh 2.6.3 and 2.5.6. Rate-limiter avoidance, access-control bypass, CPU and memory exhaustion, and replay attacks may be possible due to improper HTTP header sanitization in Envoy...

CVE-2025-21617

Guzzle OAuth Subscriber signs Guzzle requests using OAuth 1.0. Prior to 0.8.1, Nonce generation does not use sufficient entropy nor a cryptographically secure pseudorandom source. This can leave servers vulnerable to replay attacks when TLS is not used. This vulnerability is fixed in 0.8.1...

GHSA-237R-R8M4-4Q88 Guzzle OAuth Subscriber has insufficient nonce entropy

Impact Nonce generation does not use sufficient entropy nor a cryptographically secure pseudorandom source https://github.com/guzzle/oauth-subscriber/blob/0.8.0/src/Oauth1.phpL192. This can leave servers vulnerable to replay attacks when TLS is not used. Patches Upgrade to version 0.8.1 or higher...

Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)

Overview Affected versions of this package are vulnerable to Use of Cryptographically Weak Pseudo-Random Number Generator PRNG via the generateNonce function due to the insecure nonce generation process. An attacker can exploit this vulnerability to perform replay attacks when TLS is not used by...

CVE-2025-21617 Guzzle OAuth Subscriber has insufficient nonce entropy

Guzzle OAuth Subscriber signs Guzzle requests using OAuth 1.0. Prior to 0.8.1, Nonce generation does not use sufficient entropy nor a cryptographically secure pseudorandom source. This can leave servers vulnerable to replay attacks when TLS is not used. This vulnerability is fixed in 0.8.1...

CVE-2025-21617 Guzzle OAuth Subscriber has insufficient nonce entropy

Guzzle OAuth Subscriber signs Guzzle requests using OAuth 1.0. Prior to 0.8.1, Nonce generation does not use sufficient entropy nor a cryptographically secure pseudorandom source. This can leave servers vulnerable to replay attacks when TLS is not used. This vulnerability is fixed in 0.8.1...

CVE-2025-21617

CVE-2025-21617 affects the Guzzle OAuth Subscriber (PHP) where Nonce generation in OAuth 1.0 authentication did not use sufficient entropy or a cryptographically secure PRNG prior to version 0.8.1. The issue enables potential replay attacks when TLS is not used. The vulnerability is fixed in 0.8....

CVE-2025-21617 Guzzle OAuth Subscriber has insufficient nonce entropy

Guzzle OAuth Subscriber signs Guzzle requests using OAuth 1.0. Prior to 0.8.1, Nonce generation does not use sufficient entropy nor a cryptographically secure pseudorandom source. This can leave servers vulnerable to replay attacks when TLS is not used. This vulnerability is fixed in 0.8.1...

Insufficient nonce entropy

Impact Nonce generation does not use sufficient entropy nor a cryptographically secure pseudorandom source https://github.com/guzzle/oauth-subscriber/blob/0.8.0/src/Oauth1.phpL192. This can leave servers vulnerable to replay attacks when TLS is not used. Patches Upgrade to version 0.8.1 or higher...

PT-2025-4303 · Unknown · Guzzle Oauth Subscriber

Name of the Vulnerable Software and Affected Versions: Guzzle OAuth Subscriber versions prior to 0.8.1 Description: The issue concerns the Guzzle OAuth Subscriber, which signs Guzzle requests using OAuth 1.0. Prior to version 0.8.1, the Nonce generation does not utilize sufficient entropy nor a...

Guzzle 安全特征问题漏洞

Guzzle is a PHP HTTP client for guzzlehttp individual developers that makes it easy to send HTTP requests and easily integrate with web services. A Security Feature Issue vulnerability exists in Guzzle versions prior to 0.8.1 that stems from Nonce generating pseudo-random sources that do not use...

CVE-2024-56128

CVE-2024-56128 affects Apache Kafka SCRAM authentication. Root cause: SCRAM server nonce verification against the server’s first message was not performed per RFC 5802, enabling plaintext-snooping scenarios if SCRAM is used over non-TLS. Impact: exploitation requires access to plaintext SCRAM exc...

CVE-2024-56128 Apache Kafka: SCRAM authentication vulnerable to replay attacks when used without encryption

Incorrect Implementation of Authentication Algorithm in Apache Kafka's SCRAM implementation. Issue Summary: Apache Kafka's implementation of the Salted Challenge Response Authentication Mechanism SCRAM did not fully adhere to the requirements of RFC 5802 1. Specifically, as per RFC 5802, the serv...