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

> Attackers can view sensitive information in task logs, potentially exposing secrets to unauthorized users.

- **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:** 12 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-58mf-39rm-33p8

## What is CVE-2020-25825?

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

### Official description

In Octopus Deploy 3.1.0 to 2020.4.0, certain scripts can reveal sensitive information to the user in the task logs.

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

It affects 1 product.


Products: Octopus Octopus Deploy.

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

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

## Is CVE-2020-25825 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-10678](https://insights.sbomify.com/CVE-2020-10678/): Privilege escalation in n/a (high 8.8)
- [CVE-2018-5706](https://insights.sbomify.com/CVE-2018-5706/): An issue was discovered in Octopus Deploy before 4.1.9. (high 8.8)
- [CVE-2018-4862](https://insights.sbomify.com/CVE-2018-4862/): Privilege escalation in n/a (high 8.8)
- [CVE-2017-17665](https://insights.sbomify.com/CVE-2017-17665/): Missing authorization in n/a (high 8.8)
- [CVE-2019-11632](https://insights.sbomify.com/CVE-2019-11632/): Missing authorization in n/a (high 8.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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