# CVE-2023-45683: Cross site scripting via missing binding syntax validation In ACS location in github.com/crewjam/saml

> Attackers can inject JavaScript into the ACS endpoint via malicious SAML metadata, leading to XSS and potential account takeover in the IdP context.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L`)
- **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:** Yes
- **Published:** 16 Oct 2023
- **Updated:** 13 Sep 2024
- **Also known as:** GHSA-267v-3v32-g6q5, GO-2023-2114, UBUNTU-CVE-2023-45683

## What is CVE-2023-45683?

CVE-2023-45683 is a high-severity cross-site scripting vulnerability in crewjam saml, published on 16 Oct 2023. 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

github.com/crewjam/saml is a saml library for the go language. In affected versions the package does not validate the ACS Location URI according to the SAML binding being parsed. If abused, this flaw allows attackers to register malicious Service Providers at the IdP and inject Javascript in the ACS endpoint definition, achieving Cross-Site-Scripting (XSS) in the IdP context during the redirection at the end of a SAML SSO Flow. Consequently, an attacker may perform any authenticated action as the victim once the victim’s browser loaded the SAML IdP initiated SSO link for the malicious service provider. Note: SP registration is commonly an unrestricted operation in IdPs, hence not requiring particular permissions or publicly accessible to ease the IdP interoperability. This issue is fixed in version 0.4.14. Users unable to upgrade may perform external validation of URLs provided in SAML metadata, or restrict the ability for end-users to upload arbitrary metadata.

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

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

3 open source packages ship an affected version, including github.com/crewjam/saml. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/crewjam/saml` | Go | All versions | 0.4.14 |
| `github.com/crewjam/saml` | Go | All versions | 0.4.14 |
| `github.com/crewjam/saml` | Go | All versions | 0.4.14 |

Products: Saml Project Saml.

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

Upgrade github.com/crewjam/saml to 0.4.14 or later.

## Is CVE-2023-45683 being exploited?

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

## Other vulnerabilities in crewjam saml

- [CVE-2022-41912](https://insights.sbomify.com/CVE-2022-41912/): crewjam/saml go library is vulnerable to signature bypass via multiple Assertion elements (critical 9.1)
- [CVE-2023-28119](https://insights.sbomify.com/CVE-2023-28119/): crewjam/saml vulnerable to Denial Of Service Via Deflate Decompression Bomb (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-45683 is a high-severity cross-site scripting vulnerability in crewjam saml, published on 16 Oct 2023. 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-2023-45683 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/crewjam/saml (Go): affected all versions; fixed in 0.4.14
- github.com/crewjam/saml (Go): affected all versions; fixed in 0.4.14
- github.com/crewjam/saml (Go): affected all versions; fixed in 0.4.14

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-45683/ (Markdown: https://insights.sbomify.com/CVE-2023-45683/index.md)
```

## Sources

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

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