dbcve.org
Solid Edge Se2023Web browser · Siemens

CVE-2023-30985

MEDIUM · 5.5 CVSS v3.1 Published 2023-05-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 Solid Edge SE2023 (All versions < V223.0 Update 3), Solid Edge SE2023 (All versions < V223.0 Update 2). Affected applications contain an out of bounds read past the end of an allocated buffer while parsing a specially crafted OBJ file. This vulnerability could allow an attacker to disclose sensitive information. (ZDI-CAN-19426)

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

This is an out-of-bounds read vulnerability in Solid Edge SE2023's OBJ file parser. When parsing a specially crafted OBJ file, the application reads past the end of an allocated buffer, allowing disclosure of sensitive information from memory.

MitigationUpgrade Solid Edge SE2023 to version V223.0 Update 3 or later to obtain the patch for this vulnerability.

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
Solid Edge Se2023Web browser
Affected:all versions= update_0001

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 checks

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

  1. Verify Solid Edge SE2023 is installed
    Locate the Solid Edge SE2023 installation directory or check programs/features in Windows Control Panel to confirm the application is present.
    Affected if Solid Edge SE2023 is installed on the system.
  2. Determine the installed version
    Open Solid Edge SE2023 and navigate to Help > About or check the application version through the Windows installed programs list.
    Affected if Unable to determine version or version displays as SE2023.
  3. Compare version to affected range
    Identify the full version number including any update level (e.g., SE2023, SE2023 Update 1). Compare this against the fixed version V223.0 Update 3.
    Affected if The installed version is any version prior to V223.0 Update 3, including the initial release and Update_0001.
  4. Identify OBJ file handling exposure
    Confirm that the OBJ file import feature is accessible in the installed version by attempting to open or import an OBJ file through File > Open.
    Affected if OBJ file import functionality is available and the installed version is prior to V223.0 Update 3.

A user is affected if Solid Edge SE2023 is installed with any version prior to V223.0 Update 3 and the OBJ file import feature is 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Solid Edge SE2023 to version V223.0 Update 3 or later to obtain the patch for this vulnerability.

Recommended fix High confidence

V223.0 Update 3 or later

  1. Check current Solid Edge SE2023 version by opening the application and navigating to Help > About Solid Edge
  2. Download Solid Edge V223.0 Update 3 or later from the official Siemens support portal (cert-portal.siemens.com)
  3. Close all Solid Edge instances and any related processes
  4. Run the installer for V223.0 Update 3 and follow the on-screen prompts to complete the installation
  5. Restart the application and verify the version shows V223.0 Update 3 or later under Help > About Solid Edge

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

Fix this in Solid Edge Se2023 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA5.0 h
30.0 hours of engineering $5,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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