CVE-2022-24045
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 application, after a successful login, sets the session cookie on the browser via client-side JavaScript code, without applying any security attributes (such as “Secure”, “HttpOnly”, or “SameSite”). Any attempts to browse the application via unencrypted HTTP protocol would lead to the transmission of all his/her session cookies in plaintext through the network. An attacker could then be able to sniff the network and capture sensitive information.
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 confidenceIn Siemens Desigo DXR2, PXC3, PXC4, and PXC5 devices, session cookies are set via client-side JavaScript after successful login without applying the Secure, HttpOnly, or SameSite security attributes. When the application is accessed over unencrypted HTTP, session cookies are transmitted in plaintext, allowing an attacker with network proximity to capture sensitive session credentials via sniffing.
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
- 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 check the device label to confirm it is a Siemens Desigo DXR2, PXC3, PXC4, or PXC5 device.Affected if The device is not one of these four models.
-
Determine the installed firmware versionLog into the device web interface and navigate to the About or System Information page to view the firmware version. Alternatively, use the device's administration console or SNMP to query the firmware version.Affected if The firmware version falls within the affected ranges: DXR2 < 01.21.142.5-22, PXC3 < 01.21.142.4-18, PXC4 < 02.20.142.10-10884, or PXC5 < 02.20.142.10-10884.
-
Verify if the application is accessible over HTTPAttempt to access the device login page using http:// (not https://). Check if the HTTP port (typically port 80) is open and responds to requests.Affected if The device web interface is accessible over unencrypted HTTP.
-
Inspect session cookie security attributesLog into the device web interface using HTTP, open the browser developer tools (F12), go to the Application or Storage tab, and examine the session cookie. Check for the presence of Secure, HttpOnly, and SameSite attributes.Affected if The session cookie is missing one or more of the Secure, HttpOnly, or SameSite attributes.
A user is affected if they are running a vulnerable Desigo DXR2, PXC3, PXC4, or PXC5 firmware version AND the device is accessible over HTTP with session cookies lacking the Secure, HttpOnly, or SameSite attributes.
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
Enable HTTPS enforcement and configure the application to set session cookies with Secure, HttpOnly, and SameSite=Strict attributes. Update to the patched versions as specified in Siemens Security Advisory SSA-644205.
Desigo DXR2: V01.21.142.5-22 | PXC3: V01.21.142.4-18 | 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 each device
- 3. Download the appropriate firmware update from Siemens (via cert-portal.siemens.com or official Siemens support channels)
- 4. For each affected device, apply the firmware upgrade: DXR2 to V01.21.142.5-22, PXC3 to V01.21.142.4-18, PXC4/PXC5 to V02.20.142.10-10884
- 5. After upgrade, verify that session cookies are now set with appropriate security attributes (Secure, HttpOnly, SameSite)
- 6. Ensure all future access uses HTTPS instead of HTTP to prevent cookie exposure
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24045 — 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-24045 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