Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

crates.io package

enum-map

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Unratedcrates.ioPublished

    enum_map macro can cause UB when Enum trait is incorrectly implemented

    GHSA-rxhx-9fj6-6h2m

    Affected
    • crates.io enum-map >= 2.0.0-2, < 2.0.2
    Fixed in
    2.0.2· Vendor fix available
    Issue
    Affected versions of this crate did not properly check the length of an enum when using enummap! macro, trusting user-provided length. When the LENGTH in the Enum trait does not match the array length in the EnumArray trait, this can result in the initialization of the enum map with uninitialized types, which in turn can allow an attacker to execute arbitrary code. This problem can only occur with a manual implementation of the Enum trait, it will never occur for enums that use #[derive(Enum)]. Example code that triggers this vulnerability looks like this: The flaw was corrected in commit b824e23 by putting LENGTH property on sealed trait for macro to read.

    Recommended action: Upgrade to 2.0.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →