CVE-2023-1997
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 OS Command Injection vulnerability exists in SIMULIA 3DOrchestrate from Release 3DEXPERIENCE R2021x through Release 3DEXPERIENCE R2023x. A specially crafted HTTP request can lead to arbitrary command 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 confidenceOS Command Injection vulnerability in SIMULIA 3DOrchestrate allows remote attackers to execute arbitrary operating system commands through specially crafted HTTP requests. The vulnerability affects versions from 3DEXPERIENCE R2021x through R2023x, indicating a persistent flaw in input handling within the application's HTTP interface.
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= r2021x= r2022x= r2023xCVSS 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.
-
Identify if SIMULIA 3DOrchestrate or 3DEXPERIENCE is installedSearch for SIMULIA 3DOrchestrate components in your system installation directories, or check for 3DEXPERIENCE platform installation foldersAffected if SIMULIA 3DOrchestrate component is present on the system
-
Determine the installed 3DEXPERIENCE versionLocate the version information for your 3DEXPERIENCE installation (typically found in installation metadata, about dialog, or version configuration files)Affected if The version falls within the R2021x, R2022x, or R2023x release lines
-
Verify SIMULIA 3DOrchestrate service is runningCheck if the SIMULIA 3DOrchestrate service or related HTTP service is active on your systemAffected if SIMULIA 3DOrchestrate service is enabled and running
-
Confirm HTTP interface exposureInspect network configuration to determine if the 3DEXPERIENCE HTTP service is exposed to network accessAffected if The HTTP interface for SIMULIA 3DOrchestrate is accessible over the network (especially untrusted networks)
-
Review HTTP request handling configurationExamine the 3DEXPERIENCE or SIMULIA configuration files related to HTTP request processing for any non-standard input handling settingsAffected if The application accepts and processes HTTP requests without strict input validation on the 3DOrchestrate endpoint
You are affected if SIMULIA 3DOrchestrate is installed and running with a 3DEXPERIENCE version in the R2021x through R2023x range and its HTTP interface is exposed to network traffic.
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 vendor-provided patches when released; until then, implement network segmentation to restrict access to the affected service, deploy WAF rules to detect and block malicious HTTP payloads, and restrict user permissions to the principle of least privilege.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-1997 — 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-1997 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