Skip to content

phonenumber panics on parsing crafted RFC3966 inputs

High severity GitHub Reviewed Published Sep 19, 2023 in whisperfish/rust-phonenumber • Updated Nov 10, 2023

Package

cargo phonenumber (Rust)

Affected versions

< 0.2.5
>= 0.3.0, < 0.3.3

Patched versions

0.2.5
0.3.3

Description

Impact

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

Patches

Patches will be published as version 0.3.3+8.13.9 and backported as 0.2.5+8.11.3.

Workarounds

n.a.

References

n.a.

References

@rubdos rubdos published to whisperfish/rust-phonenumber Sep 19, 2023
Published by the National Vulnerability Database Sep 19, 2023
Published to the GitHub Advisory Database Sep 21, 2023
Reviewed Sep 21, 2023
Last updated Nov 10, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.100%
(42nd percentile)

Weaknesses

CVE ID

CVE-2023-42444

GHSA ID

GHSA-whhr-7f2w-qqj2

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.