# CVE-2020-8034: Cross-site scripting in n/a

> Reflected XSS in Gollem allows attackers to hijack victim webmail accounts via malicious URLs.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 18 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-8034, DLA-2229-1, GHSA-4653-jj47-h6j5, UBUNTU-CVE-2020-8034

## What is CVE-2020-8034?

CVE-2020-8034 is a medium-severity cross-site scripting vulnerability in n/a, published on 18 May 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Gollem before 3.0.13, as used in Horde Groupware Webmail Edition 5.2.22 and other products, is affected by a reflected Cross-Site Scripting (XSS) vulnerability via the HTTP GET dir parameter in the browser functionality, affecting breadcrumb output. An attacker can obtain access to a victim's webmail account by making them visit a malicious URL.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 2 products.


Products: Horde Gollem, Horde Groupware.

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

Upgrade to a fixed version.

## Is CVE-2020-8034 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-3447](https://insights.sbomify.com/CVE-2010-3447/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-8034 is a medium-severity cross-site scripting vulnerability in n/a, published on 18 May 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-8034 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-8034/ (Markdown: https://insights.sbomify.com/CVE-2020-8034/index.md)
```

## Sources

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

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