CVE-2023-46133
What it is
CryptoES is a cryptography algorithms library compatible with ES6 and TypeScript. Prior to version 2.1.0, CryptoES PBKDF2 is 1,000 times weaker than originally specified in 1993, and at least 1,300,000 times weaker than current industry standard. This is because it both defaults to SHA1, a cryptographic hash algorithm considered insecure since at least 2005, and defaults to one single iteration, a 'strength' or 'difficulty' value specified at 1,000 when specified in 1993. PBKDF2 relies on iteration count as a countermeasure to preimage and collision attacks. If used to protect passwords, the impact is high. If used to generate signatures, the impact is high. Version 2.1.0 contains a patch for this issue. As a workaround, configure CryptoES to use SHA256 with at least 250,000 iterations.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of data exposure, data tampering.
- Exploit odds
- 0.5% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.5% in the next 30 days (EPSS).
- Severity: 9.1 CRITICAL (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.5% · EPSS, next 30 days
- Weakness
- CWE-328
- Record status
- Modified
Affected
- Entronad Cryptoes < 2.1.0
Attack profile CVSS 3.1 · 9.1
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2023-46133.md and follow it. Check whether this project is affected by CVE-2023-46133. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/entronad/crypto-es/commit/d506677fae3d03a454b37ad126e0c119d416b757
- https://github.com/entronad/crypto-es/security/advisories/GHSA-mpj8-q39x-wq5h
- https://github.com/entronad/crypto-es/commit/d506677fae3d03a454b37ad126e0c119d416b757
- https://github.com/entronad/crypto-es/security/advisories/GHSA-mpj8-q39x-wq5h
References
- https://github.com/entronad/crypto-es/commit/d506677fae3d03a454b37ad126e0c119d416b757
- https://github.com/entronad/crypto-es/security/advisories/GHSA-mpj8-q39x-wq5h
- https://github.com/entronad/crypto-es/commit/d506677fae3d03a454b37ad126e0c119d416b757
- https://github.com/entronad/crypto-es/security/advisories/GHSA-mpj8-q39x-wq5h