# CVE-2016-3640: Information disclosure in n/a

> Local attackers can obtain sensitive password information from Web Dispatcher trace files in SAP HANA DB.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-gppq-cqcj-pm2v

## What is CVE-2016-3640?

CVE-2016-3640 is a medium-severity vulnerability in n/a, published on 5 Aug 2016. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Extended Application Services (aka XS or XS Engine) in SAP HANA DB 1.00.091.00.1418659308 allows local users to obtain sensitive password information via vectors related to passwords in Web Dispatcher trace files, aka SAP Security Note 2148905.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Sap Hana Db.

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

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

## Is CVE-2016-3640 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-6145](https://insights.sbomify.com/CVE-2016-6145/): Information disclosure in n/a (medium 5.3)
- [CVE-2016-3639](https://insights.sbomify.com/CVE-2016-3639/): Information disclosure in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-3640 is a medium-severity vulnerability in n/a, published on 5 Aug 2016. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-3640 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-3640/ (Markdown: https://insights.sbomify.com/CVE-2016-3640/index.md)
```

## Sources

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

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