# CVE-2021-23195: Fresenius Kabi Agilia Connect Infusion System exposure of information through directory listing

> Attackers can view server directory contents and access files if automated indexing is enabled in the Vigilant Software Suite dashboard.

- **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:** 21 Jan 2022
- **Updated:** 16 Apr 2025
- **Also known as:** GHSA-29g2-4fxx-7xmh

## What is CVE-2021-23195?

CVE-2021-23195 is a medium-severity vulnerability in Fresenius Kabi Vigilant Software Suite (Mastermed Dashboard), published on 21 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Fresenius Kabi Vigilant Software Suite (Mastermed Dashboard) version 2.0.1.3 has the option for automated indexing (directory listing) activated. When accessing a directory, a web server delivers its entire content in HTML form. If an index file does not exist and directory listing is enabled, all content of the directory will be displayed, allowing an attacker to identify and access files on the server.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), CWE-548 (Exposure of Information Through Directory Listing)

## Which versions are affected by CVE-2021-23195?

It affects 6 products.


Products: Fresenius-Kabi Agilia Connect Firmware, Fresenius-Kabi Agilia Partner Maintenance Software, Fresenius-Kabi Link\+ Agilia Firmware, Fresenius-Kabi Vigilant Centerium, Fresenius-Kabi Vigilant Insight, Fresenius-Kabi Vigilant Mastermed.

## How do I fix CVE-2021-23195?

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

## Is CVE-2021-23195 being exploited?

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

## Other vulnerabilities in Fresenius Kabi Vigilant Software Suite (Mastermed Dashboard)

- [CVE-2021-23236](https://insights.sbomify.com/CVE-2021-23236/): Fresenius Kabi Agilia Connect Infusion System uncontrolled resource consumption (high 7.5)
- [CVE-2021-23196](https://insights.sbomify.com/CVE-2021-23196/): Fresenius Kabi Agilia Connect Infusion System insufficiently protected credentials (high 7.3)
- [CVE-2021-23233](https://insights.sbomify.com/CVE-2021-23233/): Fresenius Kabi Agilia Connect Infusion System (high 7.3)
- [CVE-2021-43355](https://insights.sbomify.com/CVE-2021-43355/): Fresenius Kabi Agilia Connect Infusion System use of client side authentication (high 7.3)
- [CVE-2021-31562](https://insights.sbomify.com/CVE-2021-31562/): Fresenius Kabi Agilia Connect Infusion System use of a broken or risky cryptographic algorithm (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-23195 and fix it if it is affected.

What it is: CVE-2021-23195 is a medium-severity vulnerability in Fresenius Kabi Vigilant Software Suite (Mastermed Dashboard), published on 21 Jan 2022. 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-2021-23195 in the wild and no public exploit code.

Affected product: Fresenius Kabi Vigilant Software Suite (Mastermed Dashboard). 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-2021-23195/ (Markdown: https://insights.sbomify.com/CVE-2021-23195/index.md)
```

## Sources

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

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