rust-phonenumber: Improper Validation of Specified Quantity in Input
CVE-2023-42444 is a high-severity improper validation of specified quantity in input vulnerability in rust-phonenumber from Whisperfish, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected rust-phonenumber versions: < 0.2.5+8.11.3; >= 0.3.0, < 0.3.3+8.3.19. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.87% chance of exploitation within 30 days, higher than 59% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Phonenumber to 0.2.5\+8.11.3 or 0.3.3\+8.13.9, whichever matches your release line, or a later version.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Whisperfish | rust-phonenumber | < 0.2.5+8.11.3; >= 0.3.0, < 0.3.3+8.3.19 | Not stated |
| Whisperfish | Phonenumber | before 0.2.5\+8.11.3; 0.3.0\+8.12.9 up to, but not including, 0.3.3\+8.13.9 | 0.2.5\+8.11.3, 0.3.3\+8.13.9 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.6 | High | CNA (github.com) |
| CVSS 3.1 | 7.5 | High | NVD |
Official description
phonenumber is a library for parsing, formatting and validating international phone numbers. Prior to versions `0.3.3+8.13.9` and `0.2.5+8.11.3`, 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 over the network, specifically the string `.;phone-context=`. Versions `0.3.3+8.13.9` and `0.2.5+8.11.3` contain a patch for this issue. There are no known workarounds.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Validation of Specified Quantity in Input
The product receives input that is expected to specify a quantity (such as size or length), but it does not validate or incorrectly validates that the quantity has the required properties.
More Improper Validation of Specified Quantity in Input vulnerabilities (CWE-1284)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Other vulnerabilities in rust-phonenumber
- 8.6 High severity
Recent Improper Validation of Specified Quantity in Input vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 8.8 High severity
- 7.5 High severity
- 7.5 High severity
- 8.8 High severity
Spotted an error? Tell us.