CVE-2023-2141
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 · uneditedAn unsafe .NET object deserialization in DELMIA Apriso Release 2017 through Release 2022 could lead to post-authentication remote code execution.
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 · moderate confidenceAn unsafe .NET object deserialization vulnerability in DELMIA Apriso versions 2017 through 2022 allows authenticated attackers to deserialize untrusted data and execute arbitrary code remotely. This is a classic deserialization gadget chain exploitation in the .NET framework.
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>= 2017, <= 2022CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm DELMIA Apriso installationLocate the DELMIA Apriso installation directory. Common paths include C:\Program Files\DELMIA\Apriso or C:\3dsDialogs\Delmia\Apriso. Check for the presence of Apriso executables and configuration folders.Affected if DELMIA Apriso software is found on the system
-
Determine installed versionCheck the version of the installed DELMIA Apriso. Look for version information in the installation directory, typically in a version.txt file, or check the Windows Programs and Features list for the installed version number.Affected if The installed version matches or falls within the range of 2017 through 2022
-
Verify affected version rangeCompare your installed version number against the affected range (>= 2017 and <= 2022). Any version in this range contains the vulnerable deserialization code.Affected if The version is 2017, 2018, 2019, 2020, 2021, or 2022 (any patch level within these years)
-
Confirm application accessibilityDetermine if the DELMIA Apriso web interface or API endpoints are accessible on the network. Check if the application is running and exposed to users or external systems.Affected if The application is running and accessible to authenticated users
If DELMIA Apriso versions 2017 through 2022 are installed and the application is accessible, the environment is affected by this deserialization vulnerability.
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.
From vendor dataApply the vendor patch or update DELMIA Apriso to a patched release version. Until patched, limit access to the application to trusted users only and monitor for post-authentication indicators of compromise.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-2141 — 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-2023-2141 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