dbcve.org
Rational ClearquestApplication · Ibm

CVE-2012-0744

MEDIUM · 5.0 CVSS v2.0 Published 2012-08-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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 ClearQuest 7.1.x through 7.1.2.7 and 8.x through 8.0.0.3 allows remote attackers to obtain potentially sensitive information via a request to a (1) snoop, (2) hello, (3) ivt/, (4) hitcount, (5) HitCount.jsp, (6) HelloHTMLError.jsp, (7) HelloHTML.jsp, (8) HelloVXMLError.jsp, (9) HelloVXML.jsp, (10) HelloWMLError.jsp, (11) HelloWML.jsp, or (12) cqweb/j_security_check sample script.

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

IBM Rational ClearQuest versions 7.1.x through 7.1.2.7 and 8.x through 8.0.0.3 contain multiple sample scripts (including snoop, hello, ivt/, hitcount, various JSP files, and cqweb/j_security_check) that are accessible to remote unauthenticated attackers and can expose potentially sensitive system information, configuration details, or error messages.

MitigationRemove or disable all sample/test scripts listed in the CVE description from the ClearQuest web application, or restrict access to these endpoints via web server configuration to prevent unauthenticated access.

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 ClearquestApplication
Affected:= 7.1.1.1= 7.1.1.2= 7.1.1.3= 7.1.1.4= 7.1.1.5= 7.1.1.6= 7.1.1.7= 7.1.1.8= 7.1.2= 7.1.2.1= 7.1.2.2= 7.1.2.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
Partial
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:P/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 installed ClearQuest version
    Check the ClearQuest version through the client About dialog, web interface footer, or by querying the ClearQuest server configuration. On Windows, check the installed programs list or the ClearQuest installation directory for version information.
    Affected if The installed version is 7.1.1.1 through 7.1.2.7 in the 7.1.x line, or 8.x through 8.0.0.3 in the 8.x line.
  2. Locate sample script directories
    Inspect the ClearQuest web application deployment directory on the application server. Common paths include the cqweb or clearquest web folder within the webapps or www directory. Look for directories or files named: snoop, hello, ivt, hitcount, and any JSP files in sample or test directories.
    Affected if Any of the sample scripts (snoop, hello, ivt/, hitcount, or sample JSP files) exist in the deployed web application directory.
  3. Test unauthenticated access to sample endpoints
    From a remote system without credentials, attempt to access the suspected sample script URLs. Common patterns include: http://[server]/cqweb/snoop, http://[server]/cqweb/hello, http://[server]/cqweb/ivt/, http://[server]/cqweb/hitcount, or direct JSP file access.
    Affected if The sample scripts return HTTP 200 (success) instead of HTTP 401 (unauthorized) or HTTP 403 (forbidden), indicating they are accessible without authentication.
  4. Check for information disclosure in responses
    Review the HTTP responses from the sample endpoints. Look for system information, configuration details, file paths, error messages, or environment variables that should not be publicly visible.
    Affected if The responses contain sensitive system information, configuration details, absolute file paths, or detailed error messages that could aid an attacker.

You are affected if your ClearQuest version falls within 7.1.1.1-7.1.2.7 or 8.0.0.0-8.0.0.3 AND the sample scripts are present and accessible without authentication.

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

Remove or disable all sample/test scripts listed in the CVE description from the ClearQuest web application, or restrict access to these endpoints via web server configuration to prevent unauthenticated access.

Fix this in Rational Clearquest Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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