dbcve.org
SamlApplication · Mendix

CVE-2022-44457

CRITICAL · 9.8 CVSS v3.1 Published 2022-11-08
Fix available
A fix is available. Upgrade to 1.17.0 / 2.3.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
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.

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

A detailed technical summary for this CVE is being prepared.

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
SamlApplication
Affected:< 1.17.0>= 2.3.0, < 2.3.2>= 3.3.0, < 3.3.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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.

dbcve · scoped
Upgrade available Upgrade to 1.17.0 / 2.3.2 / 3.3.4 or later
Fixed in 1.17.02.3.23.3.4
Vendor patch cert-portal.siemens.com →
Recommended fix High confidence

Mendix SAML (Mendix 7): >= 1.17.2; Mendix SAML (Mendix 8): >= 2.3.2; Mendix SAML (Mendix 9 New Track): >= 3.3.5; Mendix SAML (Mendix 9 Upgrade Track): >= 3.3.4

  1. 1. Identify the current Mendix SAML module version and which Mendix platform track (Mendix 7, 8, or 9) and track type (New Track or Upgrade Track) is in use.
  2. 2. Download the fixed version from the Mendix App Store or Mendix Marketplace.
  3. 3. For Mendix 7 compatible: upgrade to version 1.17.2 or later.
  4. 4. For Mendix 8 compatible: upgrade to version 2.3.2 or later.
  5. 5. For Mendix 9 compatible (New Track): upgrade to version 3.3.5 or later.
  6. 6. For Mendix 9 compatible (Upgrade Track): upgrade to version 3.3.4 or later.
  7. 7. Deploy the updated module to your application and retest SAML authentication functionality.
  8. 8. If possible, review and disable the non-default 'Allow Idp Initiated Authentication' setting if not required, as an additional defense-in-depth measure.
Caveat Verify compatibility with your Mendix runtime version and test custom SAML workflows after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-44457 — 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-2022-44457 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