CVE-2014-9970

jasypt before 1.9.2 allows a timing attack against the password hash comparison...

CVE-2014-9970

jasypt before 1.9.2 allows a timing attack against the password hash comparison...

CVE-2014-9970

jasypt before 1.9.2 allows a timing attack against the password hash comparison...

CVE-2014-9970

CVE-2014-9970 affects jasypt before 1.9.2, where a timing attack can be made against password hash comparisons. The provided documents confirm the existence of this timing vulnerability but do not specify a vendor patch or fixed version within the CVE entry. The impact is described as a confident...

CVE-2014-9970

jasypt before 1.9.2 allows a timing attack against the password hash comparison...

Timing Attack

Jetty Utils is vulnerable to timing attacks. The library is vulnerable because it does not compare passwords, message digests and credentials in constant-time. This allows malicious users to use the timing of the request to progressively identify a valid passwords, message digests and credentials...

CVE-2017-7488

A flaw was found where authconfig could configure sssd in a way that treats existing and non-existing logins differently, leaking information on existence of a user. An attacker with physical or network access to the machine could enumerate users via a timing attack. Mitigation Possible workaroun...

OpenJDK: DSA implementation timing attack (Libraries, 8168728)

A covert timing channel flaw was found in the DSA implementation in the Libraries component of OpenJDK. A remote attacker could possibly use this flaw to extract certain information about the used key via a timing side channel...

Timing Attack

github.com/btcsuite/btcd is vulnerable to timing attacks. This vulnerability is caused because hashes are not compared in constant time, allowing malicious users to guess valid hashes based on the time that a comparison takes...

Timing Attack

github.com/hashicorp/vault is vulnerable to timing attacks. This vulnerability is caused because passwords are not compared in constant time, allowing malicious users to guess valid passwords based on the time that a comparison takes...

Timing Attack

github.com/openshift/origin is vulnerable to timing attacks. This vulnerability is caused because the credentials are not compared in constant time, allowing malicious users to guess the valid credentials based on the time that a comparison takes...

Timing Attack

radicale is vulnerable to timing attacks. It does not compare passwords in constant time, because it uses a non-constant character to character comparison. Consequently, the comparison will fail faster when the first characters in the password are incorrect. Attackers can exploit this difference ...

PYSEC-2017-102

Radicale before 1.1.2 and 2.x before 2.0.0rc2 is prone to timing oracles and simple brute-force attacks when using the htpasswd authentication method...

Timing Attack

github.com/bitly/oauth2proxy is vulnerable to timing attacks. This vulnerability is caused because the cookies are not compared in constant time, allowing malicious users to guess the valid cookies based on the time that a comparison takes...

Timing Attack

crypto/elliptic in github.com/golang/go is vulnerable to timing attacks. The TLS protocol implemented does not check MAC addresses in constant time when processing a malformed CBC padding. This is also known as the "Lucky Thirteen" attack...

Timing Attack

github.com/grafana/grafana is vulnerable to timing attacks. This vulnerability is caused because passwords are not validated in constant time, allowing malicious users to guess valid passwords based on the time that the validation takes...

Timing Attack

github.com/mholt/caddy is vulnerable to timing attacks. This vulnerability is caused because credentials are not compared in constant time, allowing malicious users to guess valid credentials based on the time that a comparison takes...

Timing Attack

github.com/gogits/gogs is vulnerable to timing attacks. This vulnerability is caused because passwords are not validated in constant time, allowing malicious users to guess valid passwords based on the time that a validation takes...

Timing Attacks

keycloak-core is vulnerable to timing attacks. The vulnerability is possible because the HMAC signature comparison algorithm used by its JWS token code is not performed in constant time. Therefore, an attacker can trigger a timing attack through the JWS tokens...

keycloak: timing attack in JWS signature verification

It was found that keycloak's implementation of HMAC verification for JWS tokens uses a method that runs in non-constant time, potentially leaving the application vulnerable to timing attacks...