OS Command InjectionWeakness · CWE-78

CVE-2024-1624

CRITICAL · 9.4 CVSS v3.1 Published 2024-03-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
An OS Command Injection vulnerability affecting documentation server on 3DEXPERIENCE from Release 3DEXPERIENCE R2022x through Release 3DEXPERIENCE R2024x, SIMULIA Abaqus from Release 2022 through Release 2024, SIMULIA Isight from Release 2022 through Release 2024 and CATIA Composer from Release R2023 through Release R2024. 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 · high confidence

OS Command Injection vulnerability in the documentation server component of multiple Dassault Systèmes products (3DEXPERIENCE, SIMULIA Abaqus, SIMULIA Isight, CATIA Composer). A specially crafted HTTP request allows arbitrary command execution on the underlying system.

MitigationApply vendor patches for affected releases (3DEXPERIENCE R2022x-R2024x, SIMULIA Abaqus/Isight 2022-2024, CATIA Composer R2023-R2024). Until patched, consider network segmentation to restrict access to documentation server ports.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Identify installed Dassault Systèmes products
    Check for presence of 3DEXPERIENCE, SIMULIA Abaqus, SIMULIA Isight, or CATIA Composer installations on the system. Look in common installation directories such as /opt/ or program files, or use system inventory tools.
    Affected if Any of these products are installed and version falls within R2022-R2024 for 3DEXPERIENCE, 2022-2024 for SIMULIA, or R2023-R2024 for CATIA Composer
  2. Determine installed product version
    Locate the version information from the product's about dialog, installation directory, or version file. For 3DEXPERIENCE, check the platform installation folder. For SIMULIA Abaqus/Isight, check the product version file. For CATIA Composer, check the executable or version info.
    Affected if Installed version matches the affected ranges: 3DEXPERIENCE R2022x through R2024x, SIMULIA Abaqus 2022-2024, SIMULIA Isight 2022-2024, or CATIA Composer R2023-R2024
  3. Verify documentation server component is running
    Check if the documentation server service or process is active. Look for processes related to documentation server (often named docsrv, docserver, or similar) or check running services using system utilities.
    Affected if Documentation server component is running or exposed on the network, making it reachable via HTTP requests
  4. Check for exposed documentation server ports
    Identify listening ports associated with the documentation server. Common ports may be found in product configuration files or by scanning for listening HTTP services on the host.
    Affected if Documentation server ports are accessible from network and respond to HTTP requests without authentication

The environment is affected if any of the specified Dassault Systèmes products are installed with versions R2022-R2024 and the documentation server component is exposed 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches for affected releases (3DEXPERIENCE R2022x-R2024x, SIMULIA Abaqus/Isight 2022-2024, CATIA Composer R2023-R2024). Until patched, consider network segmentation to restrict access to documentation server ports.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1624 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1624 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