# CVE-2016-6148: Code injection in n/a

> Remote attackers can execute arbitrary code or cause denial of service in SAP HANA database via malicious IMPORT statements.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 5 Aug 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-45p7-v29j-hfqf

## What is CVE-2016-6148?

CVE-2016-6148 is a high-severity code injection vulnerability in n/a, published on 5 Aug 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SAP HANA DB 1.00.73.00.389160 allows remote attackers to cause a denial of service (process termination) or execute arbitrary code via vectors related to an IMPORT statement, aka SAP Security Note 2233136.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Sap Hana.

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

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

## Is CVE-2016-6148 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-7828](https://insights.sbomify.com/CVE-2015-7828/): Auth bypass in n/a (critical 10.0)
- [CVE-2016-6143](https://insights.sbomify.com/CVE-2016-6143/): Code injection in n/a (critical 9.8)
- [CVE-2016-6150](https://insights.sbomify.com/CVE-2016-6150/): Weak cryptography in n/a (critical 9.8)
- [CVE-2016-1928](https://insights.sbomify.com/CVE-2016-1928/): Memory corruption in n/a (critical 9.8)
- [CVE-2016-1929](https://insights.sbomify.com/CVE-2016-1929/): Denial of service in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-6148 is a high-severity code injection vulnerability in n/a, published on 5 Aug 2016. 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-6148 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-6148/ (Markdown: https://insights.sbomify.com/CVE-2016-6148/index.md)
```

## Sources

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

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