Ipa up to 4.8.0 Password Hashing Long Password resource consumption

Summaryinfo

A vulnerability labeled as problematic has been found in Ipa up to 4.8.0. This issue affects some unknown processing of the component Password Hashing. Executing a manipulation as part of Long Password can lead to resource consumption. The identification of this vulnerability is CVE-2020-1722. The attack may be launched remotely. There is no exploit available.

Detailsinfo

A vulnerability has been found in Ipa up to 4.8.0 and classified as problematic. This vulnerability affects an unknown part of the component Password Hashing. The manipulation as part of a Long Password leads to a resource consumption vulnerability. The CWE definition for the vulnerability is CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. As an impact it is known to affect availability. CVE summarizes:

A flaw was found in all ipa versions 4.x.x through 4.8.0. When sending a very long password (>= 1,000,000 characters) to the server, the password hashing process could exhaust memory and CPU leading to a denial of service and the website becoming unresponsive. The highest threat from this vulnerability is to system availability.

The weakness was shared 04/27/2020 as not defined bug report (Bugzilla). The advisory is shared for download at bugzilla.redhat.com. This vulnerability was named CVE-2020-1722 since 11/27/2019. The exploitation appears to be difficult. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1499.

The vulnerability scanner Nessus provides a plugin with the ID 294770 (MiracleLinux 8 : idm:DL1 (AXSA:2021-1595:01)), which helps to determine the existence of the flaw in a target environment.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at Tenable (294770). Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• Ipa

Version

• 4.0
• 4.1
• 4.2
• 4.3
• 4.4
• 4.5
• 4.6
• 4.7
• 4.8.0

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion