# CVE-2019-10779: Cross-site scripting in stroom:stroom-app

> An attacker can hijack the Stroom UI session via XSS in a hidden iframe, allowing full control of the application on behalf of the logged-in user.

- **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:** No
- **Published:** 28 Jan 2020
- **Updated:** 4 Aug 2024
- **Also known as:** SNYK-JAVA-STROOM-541182

## What is CVE-2019-10779?

CVE-2019-10779 is a medium-severity cross-site scripting vulnerability in stroom:stroom-app, published on 28 Jan 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

All versions of stroom:stroom-app before 5.5.12 and all versions of the 6.0.0 branch before 6.0.25 are affected by Cross-site Scripting. An attacker website is able to load the Stroom UI into a hidden iframe. Using that iframe, the attacker site can issue commands to the Stroom UI via an XSS vulnerability to take full control of the Stroom UI on behalf of the logged-in user.

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

## Which versions are affected by CVE-2019-10779?

It affects 1 product.


Products: Gchq Stroom.

## How do I fix CVE-2019-10779?

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

## Is CVE-2019-10779 being exploited?

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

Public exploit code:

- GCHQ Stroom is vulnerable to Cross-Site Scripting due to the ability to load the Stroom dashboard on another site and insufficient protection against window event origins. (github_poc): https://github.com/RepublicR0K/CVE-2019-10779

## Other vulnerabilities in stroom:stroom-app

- [CVE-2018-1000651](https://insights.sbomify.com/CVE-2018-1000651/): XML external entity in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10779 and fix it if it is affected.

What it is: CVE-2019-10779 is a medium-severity cross-site scripting vulnerability in stroom:stroom-app, published on 28 Jan 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-2019-10779 in the wild and no public exploit code.

Affected product: stroom:stroom-app. 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-2019-10779/ (Markdown: https://insights.sbomify.com/CVE-2019-10779/index.md)
```

## Sources

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

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