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

> Local attackers can read insecure database permissions to access the web interface and gain root privileges on Nakivo Backup & Replication Director.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 24 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-3j3w-w8v5-3rch

## What is CVE-2020-15850?

CVE-2020-15850 is a high-severity vulnerability in n/a, published on 24 Sep 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insecure permissions in Nakivo Backup & Replication Director version 9.4.0.r43656 on Linux allow local users to access the Nakivo Director web interface and gain root privileges. This occurs because the database containing the users of the web application and the password-recovery secret value is readable.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Nakivo Backup \& Replication Director.

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

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

## Is CVE-2020-15850 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-48248](https://insights.sbomify.com/CVE-2024-48248/): NAKIVO Backup and Replication Absolute Path Traversal (high 8.6, exploited in the wild)

## Fix prompt for AI coding agents

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

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

## Sources

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

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