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

> Remote attackers can obtain authentication cookies via HTTP header reflection, potentially impersonating users if combined with XSS.

- **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:** 18 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-p2g7-qwxm-9q47

## What is CVE-2020-15768?

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

### Official description

An issue was discovered in Gradle Enterprise 2017.3 - 2020.2.4 and Gradle Enterprise Build Cache Node 1.0 - 9.2. Unrestricted HTTP header reflection in Gradle Enterprise allows remote attackers to obtain authentication cookies, if they are able to discover a separate XSS vulnerability. This potentially allows an attacker to impersonate another user. Gradle Enterprise affected application request paths:/info/headers, /cache-info/headers, /admin-info/headers, /distribution-broker-info/headers. Gradle Enterprise Build Cache Node affected application request paths:/cache-node-info/headers.

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

It affects 2 products.


Products: Gradle Enterprise, Gradle Enterprise Cache Node.

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

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

## Is CVE-2020-15768 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-49238](https://insights.sbomify.com/CVE-2023-49238/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2022-27919](https://insights.sbomify.com/CVE-2022-27919/): Missing authorization in n/a (critical 9.8)
- [CVE-2019-11402](https://insights.sbomify.com/CVE-2019-11402/): Information disclosure in n/a (critical 9.8)
- [CVE-2020-15776](https://insights.sbomify.com/CVE-2020-15776/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2022-25364](https://insights.sbomify.com/CVE-2022-25364/): Misconfiguration in n/a (high 8.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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