dbcve.org
Integration TechnologiesApplication · Sas

CVE-2023-4932

MEDIUM · 5.4 CVSS v3.1 Published 2023-12-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Reflected XSS vulnerability in SAS Web Application Server's `/SASStoredProcess/do` endpoint. The `_program` parameter lacks proper input validation, allowing injection of arbitrary JavaScript that executes in the context of an authenticated low-privileged user's browser when they open a specially crafted URL.

MitigationApply vendor hot fixes released by SAS for versions 9.4_M7 and 9.4_M8. For other versions, contact SAS to confirm vulnerability status and obtain appropriate patches.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Integration TechnologiesApplication
Affected:= 9.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm SAS Web Application Server is exposed
    Identify if the SAS web interface is accessible on your network by checking for HTTP/HTTPS responses on common SAS ports (typically 80, 443, 8080, or custom ports). Use a browser or curl to test connectivity to your SAS server URL.
    Affected if SAS Web Application Server is accessible over the network without restriction
  2. Verify the SAS version is 9.4
    Check the installed SAS Integration Technologies version. This is typically visible in SAS Management Console, in the SAS Deployment Wizard logs, or by querying the SAS metadata server. Compare your version against the affected range (9.4).
    Affected if The installed version is SAS Integration Technologies 9.4 (any sub-version)
  3. Confirm the /SASStoredProcess/do endpoint exists
    Attempt to access the endpoint by navigating to [SAS_SERVER]/SASStoredProcess/do in a browser while authenticated to SAS. A 200 response or login prompt indicates the endpoint exists and is reachable.
    Affected if The endpoint responds with a valid page or redirects to authentication, confirming the application is running
  4. Test if _program parameter accepts input
    With an authenticated session, append the parameter to the URL such as: /SASStoredProcess/do?_program=test. Observe whether the parameter value is reflected in the response without encoding or validation.
    Affected if The _program parameter value appears in the page output unescaped or without input validation, indicating potential vulnerability

A user is affected if SAS Integration Technologies version 9.4 is running and the /SASStoredProcess/do endpoint with the _program parameter is accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor hot fixes released by SAS for versions 9.4_M7 and 9.4_M8. For other versions, contact SAS to confirm vulnerability status and obtain appropriate patches.

Fix this in Integration Technologies Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-4932 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-4932 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data