# CVE-2018-2497: Information disclosure in SAP HANA

> SAP HANA fails to log SELECT events in CREATE TABLE AS SELECT statements, allowing attackers to read data without detection.

- **Severity:** Low 2.7 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mv23-4w7c-h7h7

## What is CVE-2018-2497?

CVE-2018-2497 is a low-severity vulnerability in SAP HANA, published on 11 Dec 2018. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The security audit log of SAP HANA, versions 1.0 and 2.0, does not log SELECT events if these events are part of a statement with the syntax CREATE TABLE <table_name> AS SELECT.

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

It affects 1 product.


Products: Sap Hana.

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

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

## Is CVE-2018-2497 being exploited?

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

## Other vulnerabilities in SAP HANA

- [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-2018-2497 and fix it if it is affected.

What it is: CVE-2018-2497 is a low-severity vulnerability in SAP HANA, published on 11 Dec 2018. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-2497 in the wild and no public exploit code.

Affected product: SAP HANA. 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-2497/ (Markdown: https://insights.sbomify.com/CVE-2018-2497/index.md)
```

## Sources

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

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