CVE-2022-24041
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 web application stores the PBKDF2 derived key of users passwords with a low iteration count. An attacker with user profile access privilege can retrieve the stored password hashes of other accounts and then successfully perform an offline cracking attack and recover the plaintext passwords of other users.
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 web applications in Desigo DXR2, PXC3, PXC4, and PXC5 devices store user password hashes using PBKDF2 with an insufficient iteration count. An authenticated attacker with user profile access can retrieve password hashes of other accounts and perform offline cracking attacks to recover plaintext passwords due to the weak cryptographic configuration.
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< 02.20.142.10-10884< 02.20.142.10-10884< 01.21.142.4-18< 01.21.142.5-22CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 use the device's administrative console to determine the exact model (DXR2, PXC3, PXC4, or PXC5). This information is typically displayed on the device status page or system information section of the web UI.Affected if The device is a Siemens Desigo DXR2, PXC3, PXC4, or PXC5
-
Check the installed firmware versionNavigate to the device web interface system settings or firmware information page. Compare the displayed firmware version against the affected ranges: PXC5/PXC4 < 02.20.142.10-10884, PXC3 < 01.21.142.4-18, DXR2 < 01.21.142.5-22.Affected if The firmware version is lower than the specified version for your device model
-
Verify user management web interface accessLog into the device web interface and attempt to access the user management or user profile configuration section. Check if an authenticated user with appropriate privileges can view or export user account information.Affected if The web interface exposes user account or password hash data to authenticated users with user profile access
-
Inspect password storage configurationIf accessible through the web UI or administrative console, examine the user authentication settings for any indication of PBKDF2 iteration count or cryptographic hashing configuration for passwords.Affected if The PBKDF2 iteration count is set to a low value (the vulnerability exists when the iteration count is insufficient)
A device is affected if it is a Desigo DXR2, PXC3, PXC4, or PXC5 with firmware version below the specified threshold AND the web interface allows authenticated users to access user profile data containing password hashes.
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
Upgrade to the fixed versions (DXR2: V01.21.142.5-22, PXC3: V01.21.142.4-18, PXC4/PXC5: V02.20.142.10-10884) and rehash existing user passwords with a higher PBKDF2 iteration count.
Desigo PXC3: V01.21.142.4-18 | Desigo PXC4: V02.20.142.10-10884 | Desigo PXC5: V02.20.142.10-10884 | Desigo DXR2: V01.21.142.5-22
- 1. Identify the specific Desigo device model (PXC3, PXC4, PXC5, or DXR2) in your environment
- 2. Determine the current firmware version installed on the device
- 3. For Desigo PXC3: Upgrade to firmware version 01.21.142.4-18 or later
- 4. For Desigo PXC4: Upgrade to firmware version 02.20.142.10-10884 or later
- 5. For Desigo PXC5: Upgrade to firmware version 02.20.142.10-10884 or later
- 6. For Desigo DXR2: Upgrade to firmware version 01.21.142.5-22 or later
- 7. After upgrade, verify that password hashing uses an increased PBKDF2 iteration count
- 8. Consider resetting passwords for users as a precautionary measure after patching
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,048.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24041 — 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-24041 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