dbcve.org
Cognos Tm1Application · Ibm

CVE-2012-0202

HIGH · 10.0 CVSS v2.0 Published 2012-05-04
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
High EPSS 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
Multiple stack-based buffer overflows in tm1admsd.exe in the Admin Server in IBM Cognos TM1 9.4.x and 9.5.x before 9.5.2 FP2 allow remote attackers to cause a denial of service (daemon crash) or possibly execute arbitrary code via crafted data.

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

Stack-based buffer overflow vulnerabilities exist in tm1admsd.exe (IBM Cognos TM1 Admin Server) in versions 9.4.x and 9.5.x before 9.5.2 FP2. Remote attackers can send crafted data to the Admin Server daemon, potentially causing denial of service or arbitrary code execution due to overflow on the stack.

MitigationApply IBM Cognos TM1 version 9.5.2 FP2 or later to patch the vulnerability. If immediate patching is not feasible, restrict network access to the Admin Server port using firewalls or network segmentation.

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
Cognos Tm1Application
Affected:= 9.4.1= 9.4.1.3= 9.5.1= 9.5.2

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. Verify IBM Cognos TM1 Admin Server is present
    Check for running tm1admsd.exe process or locate TM1 installation on the system
    Affected if tm1admsd.exe process is running or TM1 Admin Server is installed
  2. Determine installed IBM Cognos TM1 version
    Use system utilities or TM1 configuration tools to query the installed TM1 version number
    Affected if Version is 9.4.1, 9.4.1.3, 9.5.1, 9.5.2, or falls within 9.4.x or 9.5.x range before 9.5.2 FP2
  3. Confirm Admin Server service is network accessible
    Check if the tm1admsd.exe service is listening on network ports and accepting remote connections
    Affected if Admin Server daemon is exposed to network traffic

The environment is affected if IBM Cognos TM1 version is 9.4.1, 9.4.1.3, 9.5.1, 9.5.2, or any 9.4.x/9.5.x version prior to 9.5.2 FP2, and the Admin Server is running and accessible.

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

Apply IBM Cognos TM1 version 9.5.2 FP2 or later to patch the vulnerability. If immediate patching is not feasible, restrict network access to the Admin Server port using firewalls or network segmentation.

Recommended fix High confidence

IBM Cognos TM1 9.5.2 Fix Pack 2 (FP2) or later

  1. 1. Back up your current IBM Cognos TM1 installation and database.
  2. 2. Download IBM Cognos TM1 version 9.5.2 Fix Pack 2 (FP2) or later from IBM Fix Central (www-01.ibm.com).
  3. 3. Stop all running Cognos TM1 services, including the Admin Server (tm1admsd.exe).
  4. 4. Apply the 9.5.2 FP2 update to your existing installation.
  5. 5. Verify the update was successful by checking the version number.
  6. 6. Restart the Cognos TM1 services.
  7. 7. Test that the Admin Server functionality works correctly after the update.
Caveat Review IBM release notes for 9.5.2 FP2 for any configuration or compatibility changes before upgrading

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

Fix this in Cognos Tm1 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing12.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,220
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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