# CVE-2022-27505: Reflected cross site scripting (XSS)


- **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
- **Fix available:** No
- **Published:** 13 Apr 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-rfcv-37mc-m46j

## What is CVE-2022-27505?

CVE-2022-27505 is a medium-severity vulnerability in Citirx Citrix SD-WAN, published on 13 Apr 2022. 

### Official description

Reflected cross site scripting (XSS)

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

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

It affects 12 products.


Products: Citrix Sd-Wan 1000 Firmware, Citrix Sd-Wan 1100 Firmware, Citrix Sd-Wan 110 Firmware, Citrix Sd-Wan 2000 Firmware, Citrix Sd-Wan 2100 Firmware, Citrix Sd-Wan 210 Firmware, Citrix Sd-Wan 4000 Firmware, Citrix Sd-Wan 400 Firmware, Citrix Sd-Wan 4100 Firmware, Citrix Sd-Wan 410 Firmware, Citrix Sd-Wan 5100 Firmware, Citrix Sd-Wan 6100 Firmware.

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

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

## Is CVE-2022-27505 being exploited?

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

## Other vulnerabilities in Citirx Citrix SD-WAN

- [CVE-2024-2049](https://insights.sbomify.com/CVE-2024-2049/): Server-Side Request Forgery (SSRF) (medium 6.5)
- [CVE-2022-27506](https://insights.sbomify.com/CVE-2022-27506/): Hardcoded credentials in Citrix SD-WAN (low 2.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-27505 is a medium-severity vulnerability in Citirx Citrix SD-WAN, published on 13 Apr 2022. 
Exploitation: There is no known exploitation of CVE-2022-27505 in the wild and no public exploit code.

Affected product: Citirx Citrix SD-WAN. 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-27505/ (Markdown: https://insights.sbomify.com/CVE-2022-27505/index.md)
```

## Sources

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

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