# CVE-2015-7994: Code injection in n/a

> Remote attackers can execute arbitrary code in SAP HANA DB via SQL Login vectors, requiring a patch to mitigate.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Nov 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vjw2-8wx2-hcvh

## What is CVE-2015-7994?

CVE-2015-7994 is a high-severity code injection vulnerability in n/a, published on 10 Nov 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The SQL interface in SAP HANA DB 1.00.73.00.389160 (NewDB100_REL) allows remote attackers to execute arbitrary code via unspecified vectors related to "SQL Login," aka SAP Security Note 2197428.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2015-7994?

It affects 1 product.


Products: Sap Hana.

## How do I fix CVE-2015-7994?

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

## Is CVE-2015-7994 being exploited?

There is no known exploitation of CVE-2015-7994 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-2015-7994 and fix it if it is affected.

What it is: CVE-2015-7994 is a high-severity code injection vulnerability in n/a, published on 10 Nov 2015. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-7994 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-2015-7994/ (Markdown: https://insights.sbomify.com/CVE-2015-7994/index.md)
```

## Sources

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

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