# CVE-2016-6818: SQL injection in n/a

> Remote attackers can execute arbitrary SQL queries to read, modify, or delete data, and potentially execute OS commands in SAP Business Intelligence.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5gc3-qr3h-xrc6

## What is CVE-2016-6818?

CVE-2016-6818 is a critical SQL injection vulnerability in n/a, published on 13 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL injection vulnerability in SAP Business Intelligence platform before January 2017 allows remote attackers to obtain sensitive information, modify data, cause a denial of service (data deletion), or launch administrative operations or possibly OS commands via a crafted SQL query. The vendor response is SAP Security Note 2361633.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2016-6818?

It affects 1 product.


Products: Sap Business Intelligence Platform.

## How do I fix CVE-2016-6818?

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

## Is CVE-2016-6818 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-6818 and fix it if it is affected.

What it is: CVE-2016-6818 is a critical SQL injection vulnerability in n/a, published on 13 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-6818 in the wild and no public exploit code.

Affected product: n/a. 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-2016-6818/ (Markdown: https://insights.sbomify.com/CVE-2016-6818/index.md)
```

## Sources

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

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