secure-compare 3.0.0 and below do not actually compare two strings properly. compare was actually comparing the first argument with itself, meaning the check passed for any two strings of the same length.
References
Link | Resource |
---|---|
https://github.com/vdemedes/secure-compare/pull/1 | Third Party Advisory |
https://nodesecurity.io/advisories/50 | Third Party Advisory |
https://github.com/vdemedes/secure-compare/pull/1 | Third Party Advisory |
https://nodesecurity.io/advisories/50 | Third Party Advisory |
Configurations
History
21 Nov 2024, 02:40
Type | Values Removed | Values Added |
---|---|---|
References | () https://github.com/vdemedes/secure-compare/pull/1 - Third Party Advisory | |
References | () https://nodesecurity.io/advisories/50 - Third Party Advisory |
Information
Published : 2018-05-31 20:29
Updated : 2024-11-21 02:40
NVD link : CVE-2015-9238
Mitre link : CVE-2015-9238
CVE.ORG link : CVE-2015-9238
JSON object : View
Products Affected
secure-compare_project
- secure-compare