# CVE-2019-15897: Auth bypass in n/a

> An attacker can bypass authentication in BeeGFS by communicating with the metadata server, potentially gaining unauthorized access to the file system.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8gf9-rqhr-7hp3

## What is CVE-2019-15897?

CVE-2019-15897 is a critical authentication bypass vulnerability in n/a, published on 5 Dec 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

beegfs-ctl in ThinkParQ BeeGFS through 7.1.3 allows Authentication Bypass via communication with a BeeGFS metadata server (which is typically not exposed to external networks).

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2019-15897?

It affects 1 product.


Products: Thinkparq Beegfs.

## How do I fix CVE-2019-15897?

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

## Is CVE-2019-15897 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-15897 and fix it if it is affected.

What it is: CVE-2019-15897 is a critical authentication bypass vulnerability in n/a, published on 5 Dec 2019. 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-2019-15897 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-2019-15897/ (Markdown: https://insights.sbomify.com/CVE-2019-15897/index.md)
```

## Sources

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

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