CVE-2018-2418 json
SAP MaxDB ODBC driver (all versions before 7.9.09.07) allows an attacker to inject code that can be executed by the application.
published 8y ago modified 4mo ago also EUVD-2018-14273
- cvss
- 5.5
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
SAP MaxDB ODBC driver (all versions before 7.9.09.07) 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 maxdb_odbc_driver 7.9.09.07
Is CVE-2018-2418 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.73% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 5.5 | CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:L |
| 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 MaxDB ODBC driver
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
blogs.sap.com
/2018/05/08/sap-security-patch-day-may-2018/
vendor-advisory
-
launchpad.support.sap.com
/#/notes/2610231
permissions-required, vendor-advisory
-
securityfocus.com
/bid/104115
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-2418
- NVD CVE-2018-2418
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.