ZeroDay Findings
Sign inSign up

Findings

CVE-2024-39697

phonenumber: panic on parsing crafted phonenumber inputs

Published Jul 7, 2024 · updated Oct 13, 2026

### Impact The phonenumber parsing code may panic due to a reachable guard on the phonenumber string. In a typical deployment of rust-phonenumber, this may get triggered by feeding a maliciously crafted phonenumber, e.g. over the network, specifically strings of the form , where the "number" part potentially parses as a number larger than 2^56. Since f69abee1/0.3.4/#52. 0.2.x series is not affected. ### Patches Patches have been published as version .

Timeline

Detection, updates, and resolution for this record.

  1. Jul 7, 2024 · Catalog

    Detected

    ### Impact The phonenumber parsing code may panic due to a reachable guard on the phonenumber string. In a typical deployment of rust-phonenumber, this may get triggered by feeding a maliciously crafted phonenumber, e.g. over the network, specifically strings of the form , where the "number" part potentially parses as a number larger than 2^56. Since f69abee1/0.3.4/#52. 0.2.x series is not affecte

  2. Oct 13, 2026 · Catalog

    Fix available

    crates.io phonenumber 0.3.3 → 0.3.6

  3. Oct 13, 2026 · Catalog

    Updated

    ### Impact The phonenumber parsing code may panic due to a reachable guard on the phonenumber string. In a typical deployment of rust-phonenumber, this may get triggered by feeding a maliciously crafted phonenumber, e.g. over the network, specifically strings of the form , where the "number" part potentially parses as a number larger than 2^56. Since f69abee1/0.3.4/#52. 0.2.x series is not affecte

Affected

  • crates.io phonenumber0.3.3 → 0.3.6

Sources

References