# CVE-2019-4301: Cross-site scripting in HCL BigFix Self-Service Application (SSA)

> Attackers can execute arbitrary code by injecting JavaScript into HTML messages within the BigFix Self-Service Application.

- **Severity:** High 8.4 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-29wf-fqjv-94f8

## What is CVE-2019-4301?

CVE-2019-4301 is a high-severity cross-site scripting vulnerability in IBM Corporation HCL BigFix Self-Service Application (SSA), published on 28 Feb 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

BigFix Self-Service Application (SSA) is vulnerable to arbitrary code execution if Javascript code is included in Running Message or Post Message HTML.

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

It affects 1 product.


Products: Hcltech Self-Service Application.

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

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

## Is CVE-2019-4301 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-4301 is a high-severity cross-site scripting vulnerability in IBM Corporation HCL BigFix Self-Service Application (SSA), published on 28 Feb 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-4301 in the wild and no public exploit code.

Affected product: IBM Corporation HCL BigFix Self-Service Application (SSA). 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-4301/ (Markdown: https://insights.sbomify.com/CVE-2019-4301/index.md)
```

## Sources

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

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