CVE-2022-24042
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 returns an AuthToken that does not expire at the defined auto logoff delay timeout. An attacker could be able to capture this token and re-use old session credentials or session IDs for authorization.
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 application in Siemens Desigo DXR2, PXC3, PXC4, and PXC5 devices fails to properly expire authentication tokens at the configured auto logoff delay timeout. Session tokens remain valid indefinitely, allowing an attacker who captures a valid AuthToken to reuse it for unauthorized access even after the intended session should have expired.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 physical label to determine if the device is a Siemens Desigo DXR2, PXC3, PXC4, or PXC5Affected if The device is one of these four models
-
Check the firmware versionNavigate to the device web interface system information page or use the device management console to retrieve the installed firmware version numberAffected if The firmware version is below 02.20.142.10-10884 for PXC4/PXC5, below 01.21.142.4-18 for PXC3, or below 01.21.142.5-22 for DXR2
-
Verify web application is accessibleConfirm the device web management interface is reachable over the network on the typical HTTP/HTTPS portsAffected if The web interface is exposed and accessible
-
Check auto-logoff configurationLocate the session management or security settings in the web interface to verify whether an auto logoff timeout is configuredAffected if Auto logoff is configured but sessions remain valid after the timeout expires (this requires manual testing of session validity post-timeout)
The environment is affected if the device is a Desigo DXR2, PXC3, PXC4, or PXC5 with firmware version below the patched releases and the web interface is accessible.
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
Update affected devices to the patched versions (DXR2: V01.21.142.5-22, PXC3: V01.21.142.4-18, PXC4/PXC5: V02.20.142.10-10884). As a compensating control, implement network segmentation to limit exposure of the management interface and monitor for anomalous session activity.
Desigo PXC3: V01.21.142.4-18+ | Desigo PXC4/PXC5: V02.20.142.10-10884+ | Desigo DXR2: V01.21.142.5-22+
- Identify the exact Desigo model (PXC3, PXC4, PXC5, or DXR2) in your environment
- Check the current firmware version of the affected device
- Download the appropriate fixed firmware from Siemens (e.g., from siemens.com/support or cert-portal.siemens.com): PXC3: V01.21.142.4-18 or later | PXC4/PXC5: V02.20.142.10-10884 or later | DXR2: V01.21.142.5-22 or later
- Follow Siemens' official firmware upgrade procedure for the specific device model (typically via the device's web interface or management tool)
- After upgrade, verify the AuthToken now expires at the configured auto logoff delay timeout
- Confirm the session properly terminates after the timeout period
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.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 $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24042 — 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-24042 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