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

> Remote unauthenticated attackers can access sensitive self-diagnostic archives via a direct API request, exposing internal system information.

- **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:** 20 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-p97m-c3p6-rw68

## What is CVE-2020-24765?

CVE-2020-24765 is a high-severity vulnerability in n/a, published on 20 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

InterMind iMind Server through 3.13.65 allows remote unauthenticated attackers to read the self-diagnostic archive via a direct api/rs/monitoring/rs/api/system/dump-diagnostic-info?server=127.0.0.1 request.

Weakness: CWE-425 (Direct Request)

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

It affects 1 product.


Products: Mind Imind Server.

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

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

## Is CVE-2020-24765 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-25398](https://insights.sbomify.com/CVE-2020-25398/): Code injection in n/a (high 8.8)
- [CVE-2020-25399](https://insights.sbomify.com/CVE-2020-25399/): Cross-site scripting in n/a (high 7.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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