# CVE-2024-34923: Cross-site scripting in n/a

> Reflected cross-site scripting vulnerability in Avocent DSR and SVIP appliances allows attackers to execute scripts in user browsers.

- **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:** 27 May 2024
- **Updated:** 13 Feb 2025

## What is CVE-2024-34923?

CVE-2024-34923 is a medium-severity cross-site scripting vulnerability in n/a, published on 27 May 2024. 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

In Avocent DSR2030 Appliance firmware 03.04.00.07 before 03.07.01.23, and SVIP1020 Appliance firmware 01.06.00.03 before 01.07.00.00, there is reflected cross-site scripting (XSS).

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

## Which versions are affected by CVE-2024-34923?


## How do I fix CVE-2024-34923?

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

## Is CVE-2024-34923 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-34923 and fix it if it is affected.

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

## Sources

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

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