# CVE-2019-3686: XSS in distri and version parameter in openQA

> Attackers can inject malicious scripts via distri and version parameters in openQA, potentially leading to session hijacking or code execution.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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:** 17 Jan 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-cf2f-f2vm-48vp

## What is CVE-2019-3686?

CVE-2019-3686 is a medium-severity cross-site scripting vulnerability in SUSE openQA, published on 17 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

openQA before commit c172e8883d8f32fced5e02f9b6faaacc913df27b was vulnerable to XSS in the distri and version parameter. This was reported through the bug bounty program of Offensive Security

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

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

It affects 1 product.


Products: Suse Openqa.

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

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

## Is CVE-2019-3686 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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