# CVE-2022-44457: Auth bypass in Mendix SAML (Mendix 7 compatible)

> Attackers can bypass authentication via packet capture replay in Mendix SAML when non-default IdP-initiated authentication is enabled.

- **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:** 8 Nov 2022
- **Updated:** 1 May 2025
- **Also known as:** GHSA-r796-qqqw-vxrj

## What is CVE-2022-44457?

CVE-2022-44457 is a critical authentication bypass vulnerability in Siemens Mendix SAML (Mendix 7 compatible), published on 8 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability has been identified in Mendix SAML (Mendix 7 compatible) (All versions < V1.17.0), Mendix SAML (Mendix 7 compatible) (All versions >= V1.17.0 < V1.17.2), Mendix SAML (Mendix 8 compatible) (All versions < V2.3.0), Mendix SAML (Mendix 8 compatible) (All versions >= V2.3.0 < V2.3.2), Mendix SAML (Mendix 9 compatible, New Track) (All versions < V3.3.1), Mendix SAML (Mendix 9 compatible, New Track) (All versions >= V3.3.1 < V3.3.5), Mendix SAML (Mendix 9 compatible, Upgrade Track) (All versions < V3.3.0), Mendix SAML (Mendix 9 compatible, Upgrade Track) (All versions >= V3.3.0 < V3.3.4). Affected versions of the module insufficiently protect from packet capture replay, only when the not recommended, non default configuration option `'Allow Idp Initiated Authentication'` is enabled. This CVE entry describes the incomplete fix for CVE-2022-37011 in a specific non default configuration.

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

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

It affects 1 product.


Products: Mendix Saml.

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

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

## Is CVE-2022-44457 being exploited?

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

## Other vulnerabilities in Siemens Mendix SAML (Mendix 7 compatible)

- [CVE-2022-37011](https://insights.sbomify.com/CVE-2022-37011/): Auth bypass in Mendix SAML (Mendix 7 compatible) (critical 9.8)
- [CVE-2022-46823](https://insights.sbomify.com/CVE-2022-46823/): Cross-site scripting in Mendix SAML (Mendix 8 compatible) (critical 9.3)
- [CVE-2023-29129](https://insights.sbomify.com/CVE-2023-29129/): Auth bypass in Mendix SAML (Mendix 7 compatible) (critical 9.1)
- [CVE-2023-25957](https://insights.sbomify.com/CVE-2023-25957/): Auth bypass in Mendix SAML (Mendix 7 compatible) (critical 9.1)
- [CVE-2021-33712](https://insights.sbomify.com/CVE-2021-33712/): Auth bypass in Mendix SAML Module (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-44457 is a critical authentication bypass vulnerability in Siemens Mendix SAML (Mendix 7 compatible), published on 8 Nov 2022. 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-44457 in the wild and no public exploit code.

Affected product: Siemens Mendix SAML (Mendix 7 compatible). 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-44457/ (Markdown: https://insights.sbomify.com/CVE-2022-44457/index.md)
```

## Sources

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

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