ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2024-39697

phonenumber: panic on parsing crafted phonenumber inputs

Published Jul 7, 2024 · catalog updated Oct 13, 2026 · phonenumber: panic on parsing

Check if you run it

No confirmed exploitation is on record for CVE-2024-39697. EPSS is 0.71%. Act only if a listed version of phonenumber: panic on parsing is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (phonenumber: panic on parsing).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High8.6
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.71%
Remediation
Advisory link
Affected products
crates.io phonenumber

### 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 .

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • crates.io phonenumber0.3.3 → 0.3.6

How to fix CVE-2024-39697

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2024-39697. EPSS is 0.71%. Act only if a listed version of phonenumber: panic on parsing is installed.

Which versions are affected?

Compare what you have installed with 0.3.3 → 0.3.6. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.71%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

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 · GitHub Advisory Database

    Fix available

    phonenumber fixed in 0.3.6

  4. Oct 13, 2026 · GitHub Advisory Database

    Fix available

    phonenumber fixed in 0.3.6

  5. 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

Sources

References

Freshness

Last verified in this catalog Oct 16, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.