CVE-2022-39013 json
Under certain conditions an authenticated attacker can get access to OS credentials.
published 4y ago modified 4mo ago also EUVD-2022-41559
- cvss
- 7.6
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 54%
- public exploits
- 0
- none known
Summary
Under certain conditions an authenticated attacker can get access to OS credentials. Getting access to OS credentials enables the attacker to modify system data and make the system unavailable leading to high impact on confidentiality and low impact on integrity and availability of the application.
Is CVE-2022-39013 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
0.72% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.6 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L |
Affected products
- SAP SE SAP BusinessObjects Business Intelligence Platform (Program Objects)
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
sap.com
/documents/2022/02/fa865ea4-167e-0010-bca6-c68f7e60039b.html
vendor-advisory
-
launchpad.support.sap.com
/#/notes/3229132
permissions-required, vendor-advisory
Sources
- CVE List CVE-2022-39013
- NVD CVE-2022-39013
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.