# CVE-2021-40875: Information disclosure in n/a

> Attackers can access a public file listing application paths, potentially exposing hardcoded credentials or API keys in Gurock TestRail.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 22 Sep 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-fmj6-gcwc-6452

## What is CVE-2021-40875?

CVE-2021-40875 is a high-severity vulnerability in n/a, published on 22 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Access Control in Gurock TestRail versions < 7.2.0.3014 resulted in sensitive information exposure. A threat actor can access the /files.md5 file on the client side of a Gurock TestRail application, disclosing a full list of application files and the corresponding file paths. The corresponding file paths can be tested, and in some cases, result in the disclosure of hardcoded credentials, API keys, or other sensitive data.

Weakness: CWE-425 (Direct Request)

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

It affects 1 product.


Products: Gurock Testrail.

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

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

## Is CVE-2021-40875 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-40875 exists.

Public exploit code:

- CVE-2021-40875: Tools to Inspect Gurock Testrail Servers for Vulnerabilities related to CVE-2021-40875. (github_poc): https://github.com/SakuraSamuraii/derailed
- Python scanner for TestRail servers vulnerable to CVE-2021-40875 (github_poc): https://github.com/Lul/TestRail-files.md5-IAC-scanner
- Gurock Testrail 7.2.0.3014 - 'files.md5' Improper Access Control (exploitdb)
- Gurock TestRail Application files.md5 Exposure (nuclei): http/cves/2021/CVE-2021-40875.yaml

## Other vulnerabilities in n/a

- [CVE-2018-20063](https://insights.sbomify.com/CVE-2018-20063/): File upload in n/a (high 8.8)
- [CVE-2021-36538](https://insights.sbomify.com/CVE-2021-36538/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2021-44263](https://insights.sbomify.com/CVE-2021-44263/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2021-37788](https://insights.sbomify.com/CVE-2021-37788/): Cross-site request forgery in n/a (medium 5.4)
- [CVE-2019-7535](https://insights.sbomify.com/CVE-2019-7535/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-40875 is a high-severity vulnerability in n/a, published on 22 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-40875 exists.

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-2021-40875/ (Markdown: https://insights.sbomify.com/CVE-2021-40875/index.md)
```

## Sources

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

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