CVE-2022-24044
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 Desigo DXR2 (All versions < V01.21.142.5-22), Desigo PXC3 (All versions < V01.21.142.4-18), Desigo PXC4 (All versions < V02.20.142.10-10884), Desigo PXC5 (All versions < V02.20.142.10-10884). The login functionality of the application does not employ any countermeasures against Password Spraying attacks or Credential Stuffing attacks. An attacker could obtain a list of valid usernames on the device by exploiting the issue and then perform a precise Password Spraying or Credential Stuffing attack in order to obtain access to at least one account.
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 Desigo DXR2, PXC3, PXC4, and PXC5 building automation controllers contain a login mechanism that lacks protection against username enumeration, password spraying, and credential stuffing attacks. The application permits unlimited authentication attempts without account lockout, rate limiting, or CAPTCHA, allowing attackers to harvest valid usernames and perform brute-force attacks against them.
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< 01.21.142.5-22< 01.21.142.4-18< 02.20.142.10-10884< 02.20.142.10-10884CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 the device modelAccess the device web interface or administrative console and locate the system information or about page to confirm the exact model (DXR2, PXC3, PXC4, or PXC5)Affected if The model is one of DXR2, PXC3, PXC4, or PXC5 and falls within the affected product line
-
Determine the installed firmware versionIn the device web interface, navigate to Settings > System > Firmware or similar section to view the current firmware version numberAffected if The firmware version is below 01.21.142.5-22 for DXR2, below 01.21.142.4-18 for PXC3, or below 02.20.142.10-10884 for PXC4/PXC5
-
Verify if the web login interface is network-accessibleCheck if the device HTTP/HTTPS management port is exposed to untrusted networks by reviewing firewall rules, ACLs, or network segmentation configurationsAffected if The login page is reachable from networks outside the trusted management segment
-
Test for rate limiting on the authentication endpointSend multiple repeated login requests to the device from an external system and observe whether any throttling, rate limiting, or CAPTCHA challenge is imposedAffected if No rate limiting, CAPTCHA, or account lockout is triggered after dozens of repeated failed login attempts
-
Confirm lack of account lockout protectionAttempt to authenticate with invalid credentials multiple times (10+ attempts) using the same username and observe whether the account becomes locked or temporarily disabledAffected if The account remains active and accessible after numerous failed authentication attempts with no lockout or delay enforced
You are affected if your device is a Desigo DXR2, PXC3, PXC4, or PXC5 running firmware below the specified version thresholds AND the management interface is network-accessible with no rate limiting or account lockout protections in place.
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 · scoped01.21.142.4-1801.21.142.5-2202.20.142.10-10884
Apply vendor-supplied firmware updates (DXR2: V01.21.142.5-22, PXC3: V01.21.142.4-18, PXC4/PXC5: V02.20.142.10-10884 or later). In the interim, enforce network segmentation to restrict access to management interfaces and implement external rate-limiting or WAF controls on the authentication endpoint.
Desigo DXR2: V01.21.142.5-22 | Desigo PXC3: V01.21.142.4-18 | Desigo PXC4/PXC5: V02.20.142.10-10884
- 1. Identify the specific Desigo device model (DXR2, PXC3, PXC4, or PXC5) in your environment
- 2. Check the current firmware version of the device through the web interface or management console
- 3. Navigate to the Siemens cert-portal or official Siemens support site to download the fixed firmware: For DXR2, obtain version 01.21.142.5-22 or later; For PXC3, obtain version 01.21.142.4-18 or later; For PXC4, obtain version 02.20.142.10-10884 or later; For PXC5, obtain version 02.20.142.10-10884 or later
- 4. Follow Siemens standard firmware update procedure (typically via the device's web interface under Maintenance > Firmware Update or equivalent)
- 5. Upload and apply the firmware update to the device
- 6. After reboot, verify the firmware version has been updated successfully
- 7. Test the login functionality to confirm normal operation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24044 — 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-2022-24044 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