dbcve.org
Rational Doors Web AccessApplication · Ibm

CVE-2011-2681

HIGH · 10.0 CVSS v2.0 Published 2011-07-07
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
IBM Rational DOORS Web Access 1.4.x before 1.4.0.4 does not properly handle exceptions, which has unspecified impact and remote attack vectors.

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 Rational DOORS Web Access 1.4.x before 1.4.0.4 contains a vulnerability related to improper exception handling that can be exploited remotely, allowing attackers to potentially execute arbitrary code or cause denial of service. The specific nature of the exception handling flaw is not detailed in the available documentation.

MitigationUpgrade IBM Rational DOORS Web Access to version 1.4.0.4 or later to remediate this vulnerability. If upgrading is not immediately possible, restrict network access to the Web Access interface and monitor for suspicious 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 Doors Web AccessApplication
Affected:= 1.4= 1.4.0.1= 1.4.0.2= 1.4.0.3

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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. Locate IBM Rational DOORS Web Access installation
    Check common installation directories such as C:\Program Files\IBM\Rational\DOORS Web Access or /opt/IBM/DWA, or use system search for 'doors' or 'dwa' executables and check their properties for version information
    Affected if DOORS Web Access software is found on the system
  2. Identify installed version
    Right-click the main executable (doorswebaccess.exe or doors.exe), select Properties, and check the Version tab; alternatively, access the Web Access login page and look for version information in the About or Help section
    Affected if Version displayed is 1.4, 1.4.0.1, 1.4.0.2, or 1.4.0.3
  3. Verify web service is running
    Check if the DOORS Web Access service is running via Windows Services console (services.msc) or by attempting to access the Web Access URL (typically http://hostname:8080/dwa)
    Affected if Web Access service is active and reachable over the network
  4. Check network exposure
    Review firewall rules or network configuration to determine if the Web Access port (default 8080) is exposed to untrusted networks or the internet
    Affected if Port 8080 or the Web Access service is accessible from outside the trusted network

If DOORS Web Access version is 1.4, 1.4.0.1, 1.4.0.2, or 1.4.0.3 and the web interface is accessible, the environment is affected by CVE-2011-2681

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade IBM Rational DOORS Web Access to version 1.4.0.4 or later to remediate this vulnerability. If upgrading is not immediately possible, restrict network access to the Web Access interface and monitor for suspicious activity.

Recommended fix High confidence

1.4.0.4

  1. 1. Back up the current IBM Rational DOORS Web Access installation and configuration
  2. 2. Download IBM Rational DOORS Web Access version 1.4.0.4 from IBM Fix Central or your authorized IBM distribution channel
  3. 3. Stop the DOORS Web Access server
  4. 4. Install version 1.4.0.4 following IBM installation documentation
  5. 5. Restore any custom configurations if needed
  6. 6. Restart the DOORS Web Access server
  7. 7. Verify the application is functioning correctly and the version shows 1.4.0.4
Caveat Review IBM release notes for 1.4.0.4 for any compatibility or configuration changes from earlier 1.4.x versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rational Doors Web Access Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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