# CVE-2020-5304: Other in n/a

> Attackers can inject false log entries in WhiteSource AVM via the SAML login parameter, compromising audit integrity.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 8 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-gmq8-5gxx-6r3g

## What is CVE-2020-5304?

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

### Official description

The dashboard in WhiteSource Application Vulnerability Management (AVM) before version 20.4.1 allows Log Injection via a %0A%0D substring in the idp parameter to the /saml/login URI. This closes the current log and creates a new log with one line of data. The attacker can also insert malicious data and false entries.

Weakness: CWE-116 (Improper Encoding or Escaping of Output)

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

It affects 1 product.


Products: Whitesourcesoftware Whitesource.

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

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

## Is CVE-2020-5304 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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