# CVE-2018-2418: Code injection in SAP MaxDB ODBC driver

> An attacker can inject code into the SAP MaxDB ODBC driver to execute arbitrary commands and control application behavior.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rxg9-73c5-fc9f

## What is CVE-2018-2418?

CVE-2018-2418 is a medium-severity code injection vulnerability in SAP MaxDB ODBC driver, published on 9 May 2018. An attacker needs administrator access to exploit it, with no action from the victim.

### Official 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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2018-2418?

It affects 1 product.


Products: Sap Maxdb Odbc Driver.

## How do I fix CVE-2018-2418?

No fix has been published for CVE-2018-2418 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-2418 being exploited?

There is no known exploitation of CVE-2018-2418 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-2418 and fix it if it is affected.

What it is: CVE-2018-2418 is a medium-severity code injection vulnerability in SAP MaxDB ODBC driver, published on 9 May 2018. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-2418 in the wild and no public exploit code.

Affected product: SAP MaxDB ODBC driver. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-2418/ (Markdown: https://insights.sbomify.com/CVE-2018-2418/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-2418
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-2418
- OSV: https://osv.dev/vulnerability/CVE-2018-2418

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-2418/
Summaries are generated and may contain mistakes; the official description above is the record.