Secuno
ENNL
Book demo

CVE-2023-46133

Entronad Cryptoes vulnerability

9.1 CRITICALEPSS 0.45%
  1. Published25 Oct 2023

Description

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.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

Entronad Cryptoes< 2.1.0

Remediation

Fixed in
Entronad Cryptoes≥ 2.1.0

Frequently asked

Is CVE-2023-46133 being actively exploited?

CVE-2023-46133 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.45%.

How severe is CVE-2023-46133?

CVE-2023-46133 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.45% probability of exploitation.

Which products are affected by CVE-2023-46133?

Affected products include Entronad Cryptoes.

How do I fix CVE-2023-46133?

Upgrade affected software to a fixed version, for example Entronad Cryptoes 2.1.0 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2023-46133 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.