CVE-2024-50313
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 · uneditedA vulnerability has been identified in Mendix Runtime V10 (All versions < V10.16.0 only if the basic authentication mechanism is used by the application), Mendix Runtime V10.12 (All versions < V10.12.7 only if the basic authentication mechanism is used by the application), Mendix Runtime V10.6 (All versions < V10.6.15 only if the basic authentication mechanism is used by the application), Mendix Runtime V8 (All versions only if the basic authentication mechanism is used by the application), Mendix Runtime V9 (All versions < V9.24.29 only if the basic authentication mechanism is used by the application). The basic authentication implementation of affected applications contains a race condition vulnerability which could allow unauthenticated remote attackers to circumvent default account lockout measures.
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 · high confidenceThe Mendix Runtime basic authentication module contains a race condition that allows unauthenticated attackers to bypass account lockout protections. By exploiting timing windows in the authentication logic, attackers can submit multiple authentication attempts rapidly to circumvent lockout thresholds, enabling brute-force attacks against user credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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>= 8.0.0, < 9.24.29>= 10.0.0, < 10.6.15>= 10.7.0, < 10.12.7>= 10.13.0, < 10.16.0CVSS 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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Mendix Runtime versionCheck the Mendix Runtime version installed in your environment. This is typically found in the deployment metadata, modeler project settings, or the runtime binaries. Common locations: project settings file, deployment configuration, or runtime package manifest.Affected if The installed version falls within any of these ranges: >= 8.0.0 and < 9.24.29; >= 10.0.0 and < 10.6.15; >= 10.7.0 and < 10.12.7; >= 10.13.0 and < 10.16.0
-
Confirm basic authentication is enabledInspect the Mendix Runtime configuration or project settings to verify whether basic authentication module is active. Check authentication configuration files or the deployment model settings for basic authentication settings.Affected if Basic authentication is enabled in the Mendix Runtime configuration
-
Verify network exposure of authentication endpointDetermine if the Mendix application authentication endpoints are accessible from the network. Check firewall rules, network ACLs, and exposure of the application URLs that handle authentication requests.Affected if The authentication endpoints are externally accessible without additional rate limiting or network segmentation
You are affected if your Mendix Runtime version is within the affected ranges AND basic authentication is enabled AND the authentication endpoints are network-accessible, allowing unauthenticated attackers to attempt rapid brute-force login attempts.
Generated from the published advisory. Verify against your own configuration.
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 · scoped9.24.2910.6.1510.12.7
Upgrade Mendix Runtime to the patched versions (V10.16.0+, V10.12.7+, V10.6.15+, V9.24.29+) or disable basic authentication if not required. Consider deploying rate limiting or web application firewall rules as an interim control.
Mendix 9.24.29+ (V9), 10.6.15+ (V10.0-10.6), 10.12.7+ (V10.7-10.12), or 10.16.0+ (V10.13+)
- 1. Identify which Mendix Runtime version is currently deployed using the Mendix Developer Portal or deployment environment
- 2. Determine if your application uses basic authentication (check Mendix Studio Pro project settings > Authentication > Basic or runtime configuration for 'BasicAuthModule'
- 3. For Mendix 8.x deployments: Upgrade to Mendix 9.24.29 or later (migration to a supported version recommended as V8 is end-of-life)
- 4. For Mendix 9.x deployments: Upgrade to version 9.24.29 or later
- 5. For Mendix 10.x deployments: Upgrade to the minimum version matching your branch: 10.6.15 (for 10.0-10.6), 10.12.7 (for 10.7-10.12), or 10.16.0 (for 10.13+)
- 6. After upgrade, verify basic authentication functionality works correctly and test account lockout behavior
- 7. If upgrading is not immediately possible, consider implementing additional web application firewall (WAF) rules to mitigate brute-force attempts and monitor for suspicious authentication patterns
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50313 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-50313 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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