CVE-2022-24399 json
The SAP Focused Run (Real User Monitoring) - versions 200, 300, REST service does not sufficiently sanitize the input name of the file usin…
published 4y ago modified 4mo ago also EUVD-2022-29291
- cvss
- 6.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 72%
- public exploits
- 0
- none known
Summary
The SAP Focused Run (Real User Monitoring) - versions 200, 300, REST service does not sufficiently sanitize the input name of the file using multipart/form-data, resulting in Cross-Site Scripting (XSS) vulnerability.
Is CVE-2022-24399 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 FencerExploit prediction
1.41% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- seclists.org http://seclists.org/fulldisclosure/2022/Jun/37 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/167559/SAP-FRUN-2.00-3.00-Cross-Site-Scripting.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Affected products
- SAP SE SAP Focused Run (Real User Monitoring)
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
seclists.org
/fulldisclosure/2022/Jun/37
mailing-list, exploit, third-party-advisory
-
packetstormsecurity.com
/files/167559/SAP-FRUN-2.00-3.00-Cross-Site-Scripting.html
exploit, third-party-advisory, vdb-entry
-
dam.sap.com
/mac/embed/public/pdf/a/ucQrx6G.htm?rc=10
vendor-advisory
-
launchpad.support.sap.com
/#/notes/3147283
permissions-required, vendor-advisory
Sources
- CVE List CVE-2022-24399
- NVD CVE-2022-24399
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.