dbcve.org
Star Ccm\+Application · Siemens

CVE-2022-43517

HIGH · 7.8 CVSS v3.1 Published 2022-12-13
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 Simcenter STAR-CCM+ (All versions < V2306). The affected application improperly assigns file permissions to installation folders. This could allow a local attacker with an unprivileged account to override or modify the service executables and subsequently gain elevated 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

Simcenter STAR-CCM+ versions prior to V2306 assign overly permissive file permissions to installation folders, allowing unprivileged local users to modify or replace service executables. This enables local privilege escalation by hijacking service binary paths.

MitigationUpgrade to V2306 or later, which contains the corrected file permission settings. Alternatively, manually restrict permissions on installation directories to prevent write access by non-admin users.

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
Star Ccm\+Application
Affected:all versions

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. Verify Simcenter STAR-CCM+ installation and locate installation directory
    Search for STAR-CCM+ installation - typical paths include C:\Program Files\Siemens\ or C:\Program Files\STAR-CCM+ on Windows. Check registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Siemens\STARCCM or HKEY_LOCAL_MACHINE\SOFTWARE\MSC Software\STARCCM for install location.
    Affected if STAR-CCM+ is found to be installed in any directory
  2. Determine installed version
    Locate version information in the installation directory, typically in a version.txt file, or check the executable properties of starccm+.exe in the bin folder. Compare the version number to V2306.
    Affected if Version is prior to V2306 or version cannot be determined (treat all non-V2306 versions as affected)
  3. Check file permissions on installation directory for non-admin write access
    Right-click the STAR-CCM+ installation folder, go to Properties > Security tab. Check permissions for Users or non-admin groups. Alternatively, run: icacls "<installation_path>" | findstr /i "Users:(F)" or "Users:(OI)(CI)(F)" to detect Full Control permissions.
    Affected if Non-admin users have Full Control (F), Modify (M), or Write (W) permissions on the installation directory or its subdirectories containing service executables

User is affected if Simcenter STAR-CCM+ is installed with any version prior to V2306 and the installation directory is writable by non-privileged users, allowing potential service binary hijacking.

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

Upgrade to V2306 or later, which contains the corrected file permission settings. Alternatively, manually restrict permissions on installation directories to prevent write access by non-admin users.

Recommended fix High confidence

Simcenter STAR-CCM+ V2306 or later

  1. Identify the current version of Simcenter STAR-CCM+ installed on the system
  2. Download Simcenter STAR-CCM+ version V2306 or later from Siemens' official download portal (cert-portal.siemens.com or Siemens Support Center)
  3. Create a complete backup of all projects, simulations, and custom configurations
  4. Uninstall the current vulnerable version of STAR-CCM+
  5. Install the new version V2306 or later following Siemens installation documentation
  6. Verify the installation completed successfully and confirm the new version number
  7. Restart any STAR-CCM+ services and verify they run with correct, restricted permissions
Caveat Review Siemens release notes for V2306 to check for any changes to workflow, API compatibility, or deprecated features that may affect existing simulations or scripts

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

Fix this in Star Ccm\+ Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-43517 — 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-43517 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