dbcve.org
Xpedition DesignerApplication · Siemens

CVE-2022-31465

HIGH · 7.8 CVSS v3.1 Published 2022-06-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
A vulnerability has been identified in Xpedition Designer VX.2.10 (All versions < VX.2.10 Update 13), Xpedition Designer VX.2.11 (All versions < VX.2.11 Update 11), Xpedition Designer VX.2.12 (All versions < VX.2.12 Update 5), Xpedition Designer VX.2.13 (All versions < VX.2.13 Update 1). The affected application assigns improper access rights to the service executable. This could allow an authenticated local attacker to inject arbitrary code and escalate privileges.

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 confidence

Xpedition Designer VX assigns improper access rights to its service executable, allowing an authenticated local user to modify or replace the service binary. This enables arbitrary code injection and privilege escalation from a standard user account to elevated (SYSTEM) privileges through the service.

MitigationUpdate Xpedition Designer VX to the patched version (VX.2.10 Update 13, VX.2.11 Update 11, VX.2.12 Update 5, or VX.2.13 Update 1 or later). Alternatively, restrict write access to the service executable location to administrators only.

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
Xpedition DesignerApplication
Affected:< vx.2.11

CVSS 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Siemens Xpedition Designer is installed
    Check for the presence of Xpedition Designer in installed programs via Windows Registry (HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall) or look for the installation directory in typical locations such as C:\Siemens\ or C:\Program Files\Siemens\
    Affected if Xpedition Designer is found on the system
  2. Determine the installed version of Xpedition Designer
    Locate the version information in the installation directory or registry. Common locations include the main executable properties or README files within the Siemens\Xpedition folder
    Affected if Installed version is lower than vx.2.11 (e.g., vx.2.10, vx.2.9, or earlier)
  3. Identify the Xpedition Designer service executable
    Open Services management console (services.msc) and locate the Siemens/Xpedition service entries. Note the path to the executable listed in the service properties
    Affected if A service executable path is identified for Xpedition Designer
  4. Check write permissions on the service executable
    Right-click the service executable file, go to Properties > Security tab, and examine the Write permission entries for users or groups. Alternatively, use icacls from command line: icacls "<path_to_service_exe>"
    Affected if Standard users or authenticated users have Write or Write-Owner permissions on the service executable file
  5. Verify if the service runs with elevated privileges
    In Services management console, double-click the Xpedition Designer service and check the 'Log on as' setting. If it is set to Local System or a privileged account, the vulnerability is exploitable
    Affected if The service runs under Local System, SYSTEM, or another privileged account

A user is affected if Xpedition Designer version is below vx.2.11 AND standard users have write access to the service executable that runs with elevated privileges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Xpedition Designer VX to the patched version (VX.2.10 Update 13, VX.2.11 Update 11, VX.2.12 Update 5, or VX.2.13 Update 1 or later). Alternatively, restrict write access to the service executable location to administrators only.

Recommended fix High confidence

Xpedition Designer VX.2.13 Update 1 (or respective branch minimum: VX.2.10 Update 13, VX.2.11 Update 11, VX.2.12 Update 5)

  1. 1. Identify the currently installed Xpedition Designer version and update level
  2. 2. Based on your current version branch, determine the minimum required update: if using VX.2.10, upgrade to Update 13 or later; if VX.2.11, upgrade to Update 11 or later; if VX.2.12, upgrade to Update 5 or later; if VX.2.13, upgrade to Update 1 or later
  3. 3. Obtain the appropriate update package from Siemens support (cert-portal.siemens.com or official Siemens distribution channels)
  4. 4. Apply the update following Siemens standard installation procedures
  5. 5. Verify the update was successful by checking the application's version information

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Xpedition Designer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-31465 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-31465 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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