dbcve.org
Engineering Systems Design RhapsodyApplication · Ibm

CVE-2025-33020

HIGH · 7.5 CVSS v3.1 Published 2025-07-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
IBM Engineering Systems Design Rhapsody 9.0.2, 10.0, and 10.0.1 transmits sensitive information without encryption that could allow an attacker to obtain highly sensitive information.

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 confidence

IBM Engineering Systems Design Rhapsody versions 9.0.2, 10.0, and 10.0.1 transmits sensitive information over the network without encryption, allowing remote attackers to intercept highly sensitive data through network sniffing or man-in-the-middle attacks.

MitigationEnable TLS/SSL encryption for all network communications in IBM Rhapsody, or implement network-level encryption (VPN, IPSec) to protect data in transit.

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
Engineering Systems Design RhapsodyApplication
Affected:= 9.0.2= 10.0= 10.0.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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Identify the installed IBM Rhapsody version
    Open IBM Rhapsody and navigate to Help > About Engineering Systems Design Rhapsody, or check the installation directory for a version file. Alternatively, run 'rhapsody -version' from the command line if available.
    Affected if The installed version is 9.0.2, 10.0, or 10.0.1 - these are the affected versions listed in the CVE.
  2. Locate the network communication configuration settings
    In the IBM Rhapsody installation directory, look for configuration files such as rhapsody.ini, RhapsodyDefaults.ini, or similar settings files in the Config or etc folder. These files often contain network and communication settings.
    Affected if Network communication settings are found in plaintext configuration files without SSL/TLS encryption parameters configured.
  3. Verify whether SSL/TLS encryption is enabled for network communications
    Search the configuration files for parameters related to SSL, TLS, encryption, or secure communication. Look for settings like 'EnableSSL', 'UseEncryption', 'SecureConnection', or similar keywords. Also check if any port numbers indicate secure protocols (e.g., SSL/TLS ports).
    Affected if No SSL/TLS encryption settings are found, or encryption is explicitly disabled or set to false in the configuration.
  4. Inspect the default network port usage
    Check the configuration files or documentation for the default ports used by IBM Rhapsody for client-server communication or model repository access. Common ports include those for ClearCase, Git, or other version control integrations.
    Affected if The configured ports are standard unencrypted ports (not 443, 8443, or other known secure ports) and no encryption wrapper is documented.
  5. Review network communication logs or traces
    If available, examine any network logs, trace files, or diagnostic outputs generated by IBM Rhapsody during network operations. Look for patterns indicating unencrypted data transmission.
    Affected if Network traffic or logs show plaintext data being transmitted without encryption wrappers or protocols.

A defender is affected if their IBM Rhapsody installation matches version 9.0.2, 10.0, or 10.0.1 AND network communications are configured without SSL/TLS encryption enabled.

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

Enable TLS/SSL encryption for all network communications in IBM Rhapsody, or implement network-level encryption (VPN, IPSec) to protect data in transit.

Fix this in Engineering Systems Design Rhapsody Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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