Secuno
ENNL
Book demo

CVE-2024-36400

Viz Nano Id vulnerability

9.4 CRITICALEPSS 0.75%
  1. Published4 Jun 2024

Description

nano-id is a unique string ID generator for Rust. Affected versions of the nano-id crate incorrectly generated IDs using a reduced character set in the `nano_id::base62` and `nano_id::base58` functions. Specifically, the `base62` function used a character set of 32 symbols instead of the intended 62 symbols, and the `base58` function used a character set of 16 symbols instead of the intended 58 symbols. Additionally, the `nano_id::gen` macro is also affected when a custom character set that is not a power of 2 in size is specified. It should be noted that `nano_id::base64` is not affected by this vulnerability. This can result in a significant reduction in entropy, making the generated IDs predictable and vulnerable to brute-force attacks when the IDs are used in security-sensitive contexts such as session tokens or unique identifiers. The vulnerability is fixed in 0.4.0.

CVSS 3.1 breakdown

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

Affected products

Viz Nano Id< 0.4.0

Remediation

Fixed in
Viz Nano Id≥ 0.4.0

Frequently asked

Is CVE-2024-36400 being actively exploited?

CVE-2024-36400 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.75%.

How severe is CVE-2024-36400?

CVE-2024-36400 has a CVSS 3.1 base score of 9.4, rated critical. EPSS estimates a 0.75% probability of exploitation.

Which products are affected by CVE-2024-36400?

Affected products include Viz Nano Id.

How do I fix CVE-2024-36400?

Upgrade affected software to a fixed version, for example Viz Nano Id 0.4.0 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-36400 against the real software inventory on every managed device, every day. 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.