Security Digest · Vulnerability record

CVE-2024-39697: panic on parsing crafted phonenumber inputs

phonenumber is a library for parsing, formatting and validating international phone numbers.

CVSS 9.2 Critical EPSS 0.7% · p53

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
  • EPSS 0.7%, percentile 53: FIRST’s model estimates a 0.7% chance of exploitation activity in the next 30 days, higher than 53% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
  • Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
  • Only applies if your dependency tree includes phonenumber (crates.io (Rust)) >= 0.3.4, < 0.3.6, fixed in 0.3.6. Check your lockfile, including transitive dependencies.

What it is

phonenumber is a library for parsing, formatting and validating international phone numbers. Since 0.3.4, the phonenumber parsing code may panic due to a panic-guarded out-of-bounds access 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 +dwPAA;phone-context=AA, where the "number" part potentially parses as a number larger than 2^56. This vulnerability is fixed in 0.3.6.

From the GitHub advisory

Impact The phonenumber parsing code may panic due to a reachable assert! 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 +dwPAA;phone-context=AA, 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 Upgrade to 0.3.6 or higher.

Weakness type: CWE-284, CWE-392, CWE-1284, CWE-617, CWE-248.

Product: phonenumber (crates.io (Rust)) · Assigned by: GitHub_M · Published: 2024-07-09

Affected and fixed versions

EcosystemPackageVulnerableFirst fixed
crates.io (Rust)phonenumber>= 0.3.4, < 0.3.60.3.6
VendorProductAffected versions (per CVE record)
whisperfishrust-phonenumber>= 0.3.4, < 0.3.6

Severity scores

Scored byCVSSScoreVector
GitHub_M3.18.6 HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
GitHub4.09.2 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
  • Attack vector: network (remotely reachable)
  • Attack complexity: low
  • Attack requirements: none
  • Privileges required: none (no login)
  • User interaction: none

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
  • CISA SSVC assessment: exploitation none, automatable yes, technical impact partial.
  • FIRST EPSS (model of 2026-10-21): 0.71% probability of exploitation activity in the next 30 days; percentile 53.

Timeline

  • — CVE record published by GitHub_M
  • — GitHub-reviewed advisory GHSA-mjw4-jj88-v687 published (critical)
  • — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

  1. GitHub Advisory GHSA-mjw4-jj88-v687 github.com
  2. CVE.org record CVE-2024-39697 cve.org
  3. NVD entry CVE-2024-39697 nvd.nist.gov

Other references from the CVE record and advisory

  1. github.com github.com
  2. github.com github.com
  3. github.com github.com
  4. github.com github.com
  5. github.com github.com
  6. rustsec.org rustsec.org

Critical crates.io (Rust) advisories · Today’s Security Digest