Rational Software Architect Design ManagerApplication · Ibm

CVE-2014-0947

MEDIUM · 6.0 CVSS v2.0 Published 2014-07-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
Remotely reachable 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
Unspecified vulnerability in the server in IBM Rational Software Architect Design Manager 4.0.6 allows remote authenticated users to execute arbitrary code via a crafted update site.

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

The vulnerability exists in the server component of IBM Rational Software Architect Design Manager 4.0.6, where the update site processing mechanism fails to properly validate or sanitize content from crafted update sites. An authenticated remote attacker can exploit this to achieve arbitrary code execution on the affected server.

MitigationApply the appropriate IBM fix pack for Rational Software Architect Design Manager. Until patched, restrict update site functionality, limit authenticated user permissions to minimum required, and monitor for suspicious update site activity.

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
Rational Software Architect Design ManagerApplication
Affected:= 4.0.6

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
M
Authentication
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:S/C:P/I:P/A:P

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. Verify IBM Rational Software Architect Design Manager is installed
    Locate the installation directory or check system inventory for IBM Rational Software Architect Design Manager software
    Affected if The product is present on the system
  2. Confirm the installed version is 4.0.6
    Check the product version using the IBM installation manager, product readme, or version information file in the installation directory
    Affected if The installed version is exactly 4.0.6 (no other version is affected)
  3. Verify the server component is running
    Check for running Rational Design Manager server processes or访问 the web administration interface if available
    Affected if The server component is accessible and running
  4. Determine if update site functionality is enabled
    Review the server configuration for update site processing settings, or check if the update site feature is accessible to authenticated users
    Affected if Update site functionality is enabled and accessible to authenticated users
  5. Review authenticated user access to update site features
    Check user role assignments and permissions for update site creation or import capabilities
    Affected if Authenticated users have permissions to access or configure update sites

A user is affected if IBM Rational Software Architect Design Manager version 4.0.6 is installed with the server component running and update site functionality is enabled for authenticated users.

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 the appropriate IBM fix pack for Rational Software Architect Design Manager. Until patched, restrict update site functionality, limit authenticated user permissions to minimum required, and monitor for suspicious update site activity.

Fix this in Rational Software Architect Design Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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