Skip to content

IPAddress Infinite Loop vulnerability (Disputed)

Moderate severity GitHub Reviewed Published Dec 29, 2023 to the GitHub Advisory Database • Updated Jan 12, 2024
Withdrawn This advisory was withdrawn on Jan 12, 2024

Package

maven com.github.seancfoley:ipaddress (Maven)

Affected versions

<= 5.4.0

Patched versions

None

Description

An issue in the component IPAddressBitsDivision of IPAddress v5.1.0 leads to an infinite loop.

References

Published by the National Vulnerability Database Dec 29, 2023
Published to the GitHub Advisory Database Dec 29, 2023
Reviewed Jan 3, 2024
Withdrawn Jan 12, 2024
Last updated Jan 12, 2024

Severity

Moderate

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
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
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:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

EPSS score

0.044%
(14th percentile)

Weaknesses

CVE ID

CVE-2023-50570

GHSA ID

GHSA-qphf-w3cq-jpmx

Source code

Credits

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