safe-compare 1.1.0 vulnerabilities

Direct Vulnerabilities

Known vulnerabilities in the safe-compare package. This does not include vulnerabilities belonging to this package’s dependencies.

Fix vulnerabilities automatically

Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

Fix for free

Vulnerability	Vulnerable Version
L Timing Attack safe-compare is a Constant-time comparison algorithm to prevent Node.js timing attacks. Affected versions of this package are vulnerable to Timing Attack via the `nativeTimingSafeEqual` function which could leak the length of a user password. This is caused by always choosing the length of the longer string when comparing. How to fix Timing Attack? Upgrade `safe-compare` to version 1.1.4 or higher.	>=1.0.4 <1.1.4
M Insecure Credential Comparison `safe-compare` is a constant-time comparison algorithm to prevent timing attacks.. Affected versions of the package are vulnerable to Insecure Credential Comparison. It used the `bufferAlloc` constructor incorrectly, which caused the password string to be "padded" with itself. This means that the passwords `"a"` and `"aaaaaaaaaaaaa"` would be equal. How to fix Insecure Credential Comparison? Upgrade `safe-compare` to version 1.1.2 or higher.	>=1.1.0 <1.1.2
M Insecure Credential Comparison `safe-compare` is Constant-time comparison algorithm to prevent timing attacks.. Affected versions of the package are vulnerable to Insecure Credential Comparison due to using `String.prototype.length` instead of `Buffer.byteLength`. How to fix Insecure Credential Comparison? Upgrade `safe-compare` to version 1.1.1 or higher.	<1.1.1

Vulnerability

Vulnerable Version

Timing Attack

safe-compare is a Constant-time comparison algorithm to prevent Node.js timing attacks.

Affected versions of this package are vulnerable to Timing Attack via the nativeTimingSafeEqual function which could leak the length of a user password. This is caused by always choosing the length of the longer string when comparing.

How to fix Timing Attack?

Upgrade safe-compare to version 1.1.4 or higher.

>=1.0.4 <1.1.4

Insecure Credential Comparison

safe-compare is a constant-time comparison algorithm to prevent timing attacks..

Affected versions of the package are vulnerable to Insecure Credential Comparison. It used the bufferAlloc constructor incorrectly, which caused the password string to be "padded" with itself. This means that the passwords "a" and "aaaaaaaaaaaaa" would be equal.

How to fix Insecure Credential Comparison?

Upgrade safe-compare to version 1.1.2 or higher.

>=1.1.0 <1.1.2

Insecure Credential Comparison

safe-compare is Constant-time comparison algorithm to prevent timing attacks..

Affected versions of the package are vulnerable to Insecure Credential Comparison due to using String.prototype.length instead of Buffer.byteLength.

How to fix Insecure Credential Comparison?

Upgrade safe-compare to version 1.1.1 or higher.

<1.1.1

safe-compare@1.1.0 vulnerabilities

Constant-time comparison algorithm to prevent timing attacks.

latest version

latest non vulnerable version

first published

latest version published

licenses detected

Direct Vulnerabilities

Fix vulnerabilities automatically