# CVE-2022-45597: Security feature bypass in n/a

> The SAML2 library lacks SSL certificate validation, allowing attackers to bypass security checks during certificate exchange.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Mar 2023
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-h2q8-mvpc-6j4j

## What is CVE-2022-45597?

CVE-2022-45597 is a critical vulnerability in n/a, published on 24 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ComponentSpace.Saml2 4.4.0 Missing SSL Certificate Validation. NOTE: the vendor does not consider this a vulnerability because the report is only about use of certificates at the application layer (not the transport layer) and "Certificates are exchanged in a controlled fashion between entities within a trust relationship. This is why self-signed certificates may be used and why validating certificates isn’t as important as doing so for the transport layer certificates."

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2022-45597?

It affects 1 product.


Products: Componentspace Saml.

## How do I fix CVE-2022-45597?

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

## Is CVE-2022-45597 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-45597 and fix it if it is affected.

What it is: CVE-2022-45597 is a critical vulnerability in n/a, published on 24 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-45597 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-2022-45597/ (Markdown: https://insights.sbomify.com/CVE-2022-45597/index.md)
```

## Sources

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

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