Ping Identity PingAccess up to 8.1.0 url encoding

Summaryinfo

A vulnerability was found in Ping Identity PingAccess up to 8.1.0. It has been rated as problematic. This impacts an unknown function. Performing a manipulation results in url encoding. This vulnerability is identified as CVE-2024-23983. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability classified as problematic has been found in Ping Identity PingAccess up to 8.1.0. This affects an unknown function. The manipulation with an unknown input leads to a url encoding vulnerability. CWE is classifying the issue as CWE-177. The product does not properly handle when all or part of an input has been URL encoded. This is going to have an impact on integrity. The summary by CVE is:

Improper handling of canonical URL-encoding may lead to bypass not properly constrained by request rules.

The advisory is shared at docs.pingidentity.com. This vulnerability is uniquely identified as CVE-2024-23983 since 03/01/2024. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.

Upgrading to version 6.3.9, 7.0.8, 7.1.5, 7.2.4, 7.3.5, 8.0.4 or 8.1.1 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• Ping Identity

Name

• PingAccess

Version

• 6.3.0
• 6.3.1
• 6.3.2
• 6.3.3
• 6.3.4
• 6.3.5
• 6.3.6
• 6.3.7
• 6.3.8
• 7.0.0
• 7.0.1
• 7.0.2
• 7.0.3
• 7.0.4
• 7.0.5
• 7.0.6
• 7.0.7
• 7.1.0
• 7.1.1
• 7.1.2
• 7.1.3
• 7.1.4
• 7.2.0
• 7.2.1
• 7.2.2
• 7.2.3
• 7.3.0
• 7.3.1
• 7.3.2
• 7.3.3
• 7.3.4
• 8.0
• 8.0.0
• 8.0.1
• 8.0.2
• 8.0.3
• 8.1.0

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion