# CVE-2022-43754: SUMA/UYUNI reflected cross site scripting in /rhn/audit/scap/Search.do

> Remote attackers can inject JavaScript into SUSE Manager Server via the SCAP search page, potentially leading to session hijacking or malicious actions.

- **Severity:** Low 2.6 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 10 Nov 2022
- **Updated:** 30 Apr 2025
- **Also known as:** GHSA-vjvm-4cfh-7m4p

## What is CVE-2022-43754?

CVE-2022-43754 is a low-severity cross-site scripting vulnerability in SUSE Linux Enterprise Module for SUSE Manager Server 4.2, published on 10 Nov 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

An Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in spacewalk/Uyuni of SUSE Linux Enterprise Module for SUSE Manager Server 4.2, SUSE Linux Enterprise Module for SUSE Manager Server 4.3, SUSE Manager Server 4.2 allows remote attackers to embed Javascript code via /rhn/audit/scap/Search.do This issue affects: SUSE Linux Enterprise Module for SUSE Manager Server 4.2 hub-xmlrpc-api-0.7-150300.3.9.2, inter-server-sync-0.2.4-150300.8.25.2, locale-formula-0.3-150300.3.3.2, py27-compat-salt-3000.3-150300.7.7.26.2, python-urlgrabber-3.10.2.1py2_3-150300.3.3.2, spacecmd-4.2.20-150300.4.30.2, spacewalk-backend-4.2.25-150300.4.32.4, spacewalk-client-tools-4.2.21-150300.4.27.3, spacewalk-java-4.2.43-150300.3.48.2, spacewalk-utils-4.2.18-150300.3.21.2, spacewalk-web-4.2.30-150300.3.30.3, susemanager-4.2.38-150300.3.44.3, susemanager-doc-indexes-4.2-150300.12.36.3, susemanager-docs_en-4.2-150300.12.36.2, susemanager-schema-4.2.25-150300.3.30.3, susemanager-sls versions prior to 4.2.28. SUSE Linux Enterprise Module for SUSE Manager Server 4.3 spacewalk-java versions prior to 4.3.39. SUSE Manager Server 4.2 release-notes-susemanager versions prior to 4.2.10.

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

## Which versions are affected by CVE-2022-43754?

It affects 2 products.


Products: Suse Manager Server, Uyuni-Project Uyuni.

## How do I fix CVE-2022-43754?

Apply the vendor's patch.

## Is CVE-2022-43754 being exploited?

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

## Other vulnerabilities in SUSE Linux Enterprise Module for SUSE Manager Server 4.2

- [CVE-2023-22644](https://insights.sbomify.com/CVE-2023-22644/): JWT token compromise can allow malicious actions including Remote Code Execution (RCE) (critical 9.4)
- [CVE-2022-21952](https://insights.sbomify.com/CVE-2022-21952/): SUMA unauthenticated remote DoS via resource exhaustion (high 7.5)
- [CVE-2022-31248](https://insights.sbomify.com/CVE-2022-31248/): SUMA user enumeration via weak error message (medium 5.3)
- [CVE-2022-31255](https://insights.sbomify.com/CVE-2022-31255/): SUMA/UYUNI directory path traversal vulnerability in CobblerSnipperViewAction (medium 4.3)
- [CVE-2022-43753](https://insights.sbomify.com/CVE-2022-43753/): SUMA/UYUNI arbitrary file disclosure vulnerability in ScapResultDownload (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-43754 and fix it if it is affected.

What it is: CVE-2022-43754 is a low-severity cross-site scripting vulnerability in SUSE Linux Enterprise Module for SUSE Manager Server 4.2, published on 10 Nov 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-43754 in the wild and no public exploit code.

Affected product: SUSE Linux Enterprise Module for SUSE Manager Server 4.2. 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-2022-43754/ (Markdown: https://insights.sbomify.com/CVE-2022-43754/index.md)
```

## Sources

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

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