dbcve.org
Simcenter AmesimApplication · Siemens

CVE-2023-43625

CRITICAL · 9.8 CVSS v3.1 Published 2023-10-10
Fix available
A fix is available. Upgrade to 2021.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Amesim (All versions < V2021.1). The affected application contains a SOAP endpoint that could allow an unauthenticated remote attacker to perform DLL injection and execute arbitrary code in the context of the affected application process.

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 Amesim versions prior to V2021.1 contain an insecure SOAP endpoint that lacks authentication controls, allowing unauthenticated remote attackers to inject malicious DLLs and execute arbitrary code within the application's process context.

MitigationUpgrade Simcenter Amesim to version V2021.1 or later to obtain the patched SOAP endpoint; if upgrading is not feasible, disable or restrict access to the SOAP service and implement network segmentation.

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
Simcenter AmesimApplication
Affected:< 2021.1

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate Simcenter Amesim installation
    Search for Amesim installation directories (commonly under C:\Program Files\Siemens or C:\Program Files (x86)\Siemens) or check registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Siemens\Simcenter\Amesim for the installation path
    Affected if Simcenter Amesim is installed on the system
  2. Identify installed Amesim version
    Locate version information in the installation directory, typically in a version.txt, about.ini, or product.xml file within the Amesim program folder, or via 'Add/Remove Programs' in Control Panel
    Affected if The installed version is earlier than V2021.1 (e.g., V2020, V2019, etc.)
  3. Verify SOAP service status
    Check for running processes related to SOAP services (look for AmesimSOAP, amesim_soap, or similar processes in Task Manager) and examine Windows Services for any Amesim-related SOAP services
    Affected if The SOAP service process is running or the SOAP Windows service is present and enabled
  4. Inspect SOAP endpoint configuration
    Search for SOAP configuration files in the Amesim installation directory (look for soap.ini, webservices.cfg, or similar XML/INI files under a 'conf' or 'config' subfolder) and examine bind address or authentication settings
    Affected if The SOAP endpoint is configured to allow remote connections without authentication (no user/password required, bind address set to 0.0.0.0 or accessible externally)

A system is affected if Simcenter Amesim version earlier than V2021.1 is installed AND the unauthenticated SOAP endpoint service is enabled and accessible.

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
Upgrade available Upgrade to 2021.1 or later
Fixed in 2021.1
Interim mitigation

Upgrade Simcenter Amesim to version V2021.1 or later to obtain the patched SOAP endpoint; if upgrading is not feasible, disable or restrict access to the SOAP service and implement network segmentation.

Recommended fix High confidence

2021.1

  1. 1. Back up all Simcenter Amesim projects, custom models, and configurations before making changes
  2. 2. Obtain Simcenter Amesim version 2021.1 or later from the Siemens Support portal (cert-portal.siemens.com or sw.siemens.com)
  3. 3. Uninstall the current vulnerable version of Simcenter Amesim
  4. 4. Install Simcenter Amesim version 2021.1 following the Siemens installation documentation
  5. 5. Restore backed-up projects and configurations to the new installation
  6. 6. Verify that the SOAP endpoint vulnerability is resolved by confirming the application functions normally and reviewing release notes for security fixes
Caveat Review the 2021.1 release notes for any model compatibility changes or deprecated features that may affect existing simulations

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

Fix this in Simcenter Amesim Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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