CVE-2019-0247 json
SAP Cloud Connector, before version 2.11.3, allows an attacker to inject code that can be executed by the application.
published 7y ago modified 4mo ago also EUVD-2019-1020
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 0
- none known
Summary
SAP Cloud Connector, before version 2.11.3, allows an attacker to inject code that can be executed by the application. An attacker could thereby control the behavior of the application.
Patch / fix
- sap cloud_connector 2.11.3
Is CVE-2019-0247 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.27% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- SAP SE SAP Cloud Connector
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
launchpad.support.sap.com
/#/notes/2696233
permissions-required, vendor-advisory
-
wiki.scn.sap.com
/wiki/pages/viewpage.action?pageId=509151985
vendor-advisory
Sources
- CVE List CVE-2019-0247
- NVD CVE-2019-0247
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.