CVE-2025-33077
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 · uneditedIBM Engineering Systems Design Rhapsody 9.0.2, 10.0, and 10.0.1 is vulnerable to a stack-based buffer overflow, caused by improper bounds checking. A local user could overflow the buffer and execute arbitrary code on the system.
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 confidenceStack-based buffer overflow in IBM Engineering Systems Design Rhapsody versions 9.0.2 through 10.0.1 caused by improper bounds checking, allowing a local authenticated user to overflow a stack-allocated buffer and execute arbitrary code with the privileges of the running process.
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= 9.0.2= 10.0= 10.0.1CVSS 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.
-
Verify IBM Engineering Systems Design Rhapsody is installedCheck for Rhapsody installation by looking in typical installation directories such as C:\Program Files\IBM\Rhapsody or C:\Program Files (x86)\IBM\Rhapsody, or use system inventory tools to find the productAffected if Rhapsody is not installed on the system
-
Determine the installed Rhapsody versionOpen the Rhapsody application and navigate to Help > About IBM Engineering Systems Design Rhapsody, or locate the version info in the installation directory's release notes or version.xml fileAffected if The installed version matches 9.0.2, 10.0, or 10.0.1 exactly
-
Compare your version against the affected rangeDocument the exact version number and compare against the affected range: version 9.0.2 through 10.0.1 inclusiveAffected if The installed version falls within 9.0.2 to 10.0.1 inclusive (including the exact versions listed)
-
Identify the user context where Rhapsody executesCheck the account or user context under which the Rhapsody process runs by reviewing service configuration (if running as a service) or the logged-in user session when launching the applicationAffected if The process runs with elevated or privileged account credentials, as exploitation allows code execution with the privileges of the running process
You are affected if IBM Engineering Systems Design Rhapsody versions 9.0.2, 10.0, or 10.0.1 are installed and running on your system.
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 IBM's security patch or upgrade to a version beyond 10.0.1; validate the fix in a staging environment before production deployment to ensure functional compatibility.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-33077 — 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-2025-33077 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