# CVE-2023-4932: Reflected Cross-Site Scripting in SAS 9.4


- **Severity:** Medium 6.3 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 12 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-v68r-h54c-vpg9

## What is CVE-2023-4932?

CVE-2023-4932 is a medium-severity vulnerability in SAS Integration Technologies, published on 12 Dec 2023. 

### Official description

SAS application is vulnerable to Reflected Cross-Site Scripting (XSS). Improper input validation in the `_program` parameter of the the `/SASStoredProcess/do` endpoint allows arbitrary JavaScript to be executed when specially crafted URL is opened by an authenticated user. The attack is possible from a low-privileged user. Only versions 9.4_M7 and 9.4_M8 were tested and confirmed to be vulnerable, status of others is unknown. For above mentioned versions hot fixes were published.

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

## Which versions are affected by CVE-2023-4932?

It affects 1 product.


Products: Sas Integration Technologies.

## How do I fix CVE-2023-4932?

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

## Is CVE-2023-4932 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-4932 and fix it if it is affected.

What it is: CVE-2023-4932 is a medium-severity vulnerability in SAS Integration Technologies, published on 12 Dec 2023. 
Exploitation: There is no known exploitation of CVE-2023-4932 in the wild and no public exploit code.

Affected product: SAS Integration Technologies. 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-2023-4932/ (Markdown: https://insights.sbomify.com/CVE-2023-4932/index.md)
```

## Sources

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

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