# CVE-2020-7959: Information disclosure in n/a

> Attackers can enumerate database names via error messages in LabVantage LIMS, exposing sensitive infrastructure details.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-p6hf-7wm2-3xg4

## What is CVE-2020-7959?

CVE-2020-7959 is a medium-severity vulnerability in n/a, published on 17 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

LabVantage LIMS 8.3 does not properly maintain the confidentiality of database names. For example, the web application exposes the database name. An attacker might be able to enumerate database names by providing his own database name in a request, because the response will return an 'Unrecognized Database exception message if the database does not exist.

Weakness: CWE-203 (Observable Discrepancy)

## Which versions are affected by CVE-2020-7959?

It affects 1 product.


Products: Labvantage Labvantage.

## How do I fix CVE-2020-7959?

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

## Is CVE-2020-7959 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-7959 and fix it if it is affected.

What it is: CVE-2020-7959 is a medium-severity vulnerability in n/a, published on 17 Feb 2020. 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-2020-7959 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-2020-7959/ (Markdown: https://insights.sbomify.com/CVE-2020-7959/index.md)
```

## Sources

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

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