Norman API Cross-site Scripting Vulnerability
CVE-2023-32193GHSA-r8f4-hv23-6qp6
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/rancher/norman 0.0.0-20240207153100-3bb70b772b52), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
- Affected
- < 0.0.0-20240207153100-3bb70b772b52
- Fixed in
- 0.0.0-20240207153100-3bb70b772b52
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-r8f4-hv23-6qp6 lists affected ranges: Go github.com/rancher/norman >=0 <0.0.0-20240207153100-3bb70b772b52
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 8.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L
- EPSS
- CVE-2023-32193: 0.47% estimated exploitation activity in the next 30 days; percentile 40.47 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Impact A vulnerability has been identified in which unauthenticated cross-site scripting (XSS) in Norman's public API endpoint can be exploited. This can lead to an attacker exploiting the vulnerability to trigger JavaScript code and execute commands remotely. The attack vector was identified as a Reflected XSS. Norman API propagates malicious payloads from user input to the UI, which renders the output. For example, a malicious URL gets rendered into a script that is executed on a page. The changes addressed by this fix are: - Encode input that comes from the request URL before adding it to the response. - The request input is escaped by changing the URL construction that is used for links to use url.URL. - The request input is escaped by escaping the JavaScript and CSS variables with attribute encoding as defined by OWASP. Patches Patched versions include the following commits: | Branch | Commit | | -------- | ------- | | master | 3bb70b7 | | release/v2.8 | a6a6cf5 | | release/v2.7…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-r8f4-hv23-6qp6
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2023-32193 Advisory: Norman API Cross-site Scripting Vulnerability IDs: CVE-2023-32193, GHSA-r8f4-hv23-6qp6 Record: https://patchnext.com/advisories/cve-2023-32193 (revision 1, source checked 26 Oct 2026, 15:05 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 8.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/rancher/norman 0.0.0-20240207153100-3bb70b772b52. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/rancher/norman: affected < 0.0.0-20240207153100-3bb70b772b52; fixed in 0.0.0-20240207153100-3bb70b772b52 ## Suggested inspection (read-only) - Go github.com/rancher/norman: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/rancher/norman. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-r8f4-hv23-6qp6 (GitHub-reviewed advisory GHSA-r8f4-hv23-6qp6 lists affected ranges: Go github.com/rancher/norman >=0 <0.0.0-20240207153100-3bb70b772b52) Commands are suggestions: review each one before running it.
Loading voting…