# CVE-2019-17115: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script via unsanitized parameters in WiKID 2FA Enterprise Server, leading to potential session hijacking or malicious actions.

- **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:** 17 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-v69q-7f8j-w29w

## What is CVE-2019-17115?

CVE-2019-17115 is a medium-severity cross-site scripting vulnerability in n/a, published on 17 Oct 2019. 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

Multiple cross-site scripting (XSS) vulnerabilities in WiKID 2FA Enterprise Server through 4.2.0-b2047 allow remote attackers to inject arbitrary web script or HTML that is triggered when Logs.jsp is visited. The rendered_message column is retrieved and displayed, unsanitized, on Logs.jsp. A remote attack can populate the rendered_message column with malicious values via: (1) H parameter to /wikid/servlet/com.wikidsystems.server.GetDomainHash (2) S parameter to: - /wikid/DomainData - /wikid/PreRegisterLookup - /wikid/PreRegister - /wikid/InitDevice - /wikid/servlet/InitDevice2S - /wikid/servlet/InitDevice3S - /servlet/com.wikidsystems.server.InitDevice2S - /servlet/com.wikidsystems.server.InitDevice3S - /servlet/com.wikidsystems.server.InitDevice4S - /wikid/servlet/com.wikidsystems.server.InitDevice4AES - /wikid/servlet/com.wikidsystems.server.InitDevice5AES (3) a parameter to: - /wikid/PreRegisterLookup - /wikid/InitDevice - /wikid/servlet/InitDevice2S - /wikid/servlet/InitDevice3S - /servlet/com.wikidsystems.server.InitDevice2S - /servlet/com.wikidsystems.server.InitDevice3S - /servlet/com.wikidsystems.server.InitDevice4S - /wikid/servlet/com.wikidsystems.server.InitDevice4AES - /wikid/servlet/com.wikidsystems.server.InitDevice5AES.

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

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

It affects 1 product.


Products: Wikidsystems Two Factor Authentication Enterprise Server.

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

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

## Is CVE-2019-17115 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-16917](https://insights.sbomify.com/CVE-2019-16917/): SQL injection in n/a (high 8.8)
- [CVE-2019-17119](https://insights.sbomify.com/CVE-2019-17119/): SQL injection in n/a (high 8.8)
- [CVE-2019-17114](https://insights.sbomify.com/CVE-2019-17114/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2019-17116](https://insights.sbomify.com/CVE-2019-17116/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-17115 is a medium-severity cross-site scripting vulnerability in n/a, published on 17 Oct 2019. 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-17115 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-2019-17115/ (Markdown: https://insights.sbomify.com/CVE-2019-17115/index.md)
```

## Sources

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

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