org.wildfly.security:wildfly-elytron-password-impl@2.0.0.Alpha10

latest version

2.9.2.SP1

first published

7 years ago

latest version published

2 days ago

licenses detected

Apache-2.0
[1.9.0.CR1,)

package registry

View on Maven Central Repository

Go back to all versions of this package

Report a new vulnerability Found a mistake?

Direct Vulnerabilities

Known vulnerabilities in the org.wildfly.security:wildfly-elytron-password-impl 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

Vulnerability	Vulnerable Version
C Improper Handling of Alternate Encoding Affected versions of this package are vulnerable to Improper Handling of Alternate Encoding in its password normalization, which applies Unicode NFKC (compatibility) normalization before hashing and so folds fullwidth and other compatibility characters to their ASCII equivalents. An attacker with access to the stored password hashes can shrink the effective keyspace and test ASCII dictionary candidates against passwords originally set with compatibility characters, since distinct inputs such as `Ａ` (U+FF21) and `A` (U+0041) produce the same hash. This affects only credentials whose passwords contain compatibility characters such as fullwidth letters or digits, and the attacker must already possess the hashes to run the offline dictionary attack. How to fix Improper Handling of Alternate Encoding? A fix was pushed into the `master` branch but not yet published.	[0,)

Improper Handling of Alternate Encoding

Affected versions of this package are vulnerable to Improper Handling of Alternate Encoding in its password normalization, which applies Unicode NFKC (compatibility) normalization before hashing and so folds fullwidth and other compatibility characters to their ASCII equivalents. An attacker with access to the stored password hashes can shrink the effective keyspace and test ASCII dictionary candidates against passwords originally set with compatibility characters, since distinct inputs such as Ａ (U+FF21) and A (U+0041) produce the same hash. This affects only credentials whose passwords contain compatibility characters such as fullwidth letters or digits, and the attacker must already possess the hashes to run the offline dictionary attack.

How to fix Improper Handling of Alternate Encoding?

A fix was pushed into the master branch but not yet published.

[0,)

Go back to all versions of this package