PingFederate REST API Data Store Injection

published 2024-07-09 2y ago modified 2026-06-17 4mo ago also EUVD-2024-19444

cvss: 3.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.2%; EPSS 0.2% chance of exploitation in 30 days, percentile 14%
public exploits: 0; none known

A potential JSON injection attack vector exists in PingFederate REST API data stores using the POST method and a JSON request body.

Is CVE-2024-21832 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 2y ago (2024-07-10)

Exploit prediction

0.24% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by	version	score	vector
CNA	3.1	3.5	CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:N

Affected products

Ping Identity PingFederate

Classification

Weakness

CWE-94 Improper Control of Generation of Code

References

docs.pingidentity.com /r/en-us/pingfederate-120/lwu1707324350083

Sources

CVE List CVE-2024-21832
NVD CVE-2024-21832

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.