Cognos Disclosure ManagementApplication · Ibm

CVE-2013-0501

HIGH · 9.3 CVSS v2.0 Published 2013-04-12

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

NVD · unedited

The EdrawSoft EDOFFICE.EDOfficeCtrl.1 ActiveX control, as used in Edraw Office Viewer Component, the client in IBM Cognos Disclosure Management (CDM) 10.2.0, and other products, allows remote attackers to read arbitrary files, or download an arbitrary program onto a client machine and execute this program, via a crafted web site.

Technical summary

dbcve analysis · high confidence

The EdrawSoft EDOFFICE.EDOfficeCtrl.1 ActiveX control contains multiple critical vulnerabilities allowing remote attackers to read arbitrary files from the client system and to download and execute arbitrary programs. This is a classic ActiveX unsafe for scripting vulnerability that can be exploited via malicious web pages, making it particularly dangerous for any organization using affected products.

MitigationDisable the vulnerable ActiveX control via browser security settings or Group Policy, or remove/uninstall the affected Edraw Office Viewer Component and IBM Cognos Disclosure Management products if no vendor patch is available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Cognos Disclosure ManagementApplication

Affected:= 10.2.0

CVSS breakdown

From the vector

Attack vector: Network
Complexity: M
Authentication: None
Confidentiality: Complete
Integrity: Complete
Availability: Complete

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

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Check for IBM Cognos Disclosure Management installation

Open Windows Control Panel, go to Programs and Features, or run 'wmic product get name,version' to list installed software. Look for 'IBM Cognos Disclosure Management' with version 10.2.0.

Affected if IBM Cognos Disclosure Management version 10.2.0 is installed on the system
Verify EdrawSoft ActiveX control presence in registry

Open Registry Editor (regedit), navigate to HKEY_CLASSES_ROOT\CLSID and search for '{0D6D8D8B-9B55-4E8D-B7F2-1C2E7A8C9D3E}' or the CLSID for EDOFFICE.EDOfficeCtrl.1. You can also check HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Code Store Database\Distribution Units for the control.

Affected if The EdrawSoft EDOFFICE.EDOfficeCtrl.1 ActiveX control CLSID is registered on the system
Check if ActiveX control is marked safe for scripting

In Registry Editor, look under HKEY_CLASSES_ROOT\CLSID\{CLSID}\Implemented Categories\{7DD95801-9882-11CF-9FA9-00AA006C42C4} where {CLSID} is the EDOFFICE.EDOfficeCtrl.1 CLSID. The presence of this key indicates the control is marked Safe for Scripting.

Affected if The ActiveX control is registered with Safe for Scripting category, making it exploitable via malicious web pages
Inspect browser security zone settings

Open Internet Explorer (if available), go to Internet Options > Security > Custom Level. Scroll to 'ActiveX controls and plugins' section. Check settings for 'Initialize and script ActiveX controls not marked as safe for scripting'.

Affected if The browser security settings allow initialization of ActiveX controls not marked as safe, or if IE is used with this control allowed in trust zones
Search for Edraw Office Viewer Component files

Check common installation paths such as C:\Program Files\EdrawSoft\ or C:\Program Files\IBM\Cognos\Disclosure Management\ for files related to Edraw Office Viewer Component. Use File Explorer or command: dir /s "C:\Program Files\*Edraw*"

Affected if Edraw Office Viewer Component files are found on the system, particularly in Cognos Disclosure Management installation directories

A system is affected if IBM Cognos Disclosure Management 10.2.0 is installed AND the EdrawSoft EDOFFICE.EDOfficeCtrl.1 ActiveX control is registered, especially if marked as Safe for Scripting in the registry.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Disable the vulnerable ActiveX control via browser security settings or Group Policy, or remove/uninstall the affected Edraw Office Viewer Component and IBM Cognos Disclosure Management products if no vendor patch is available.

Recommended fix Moderate confidence

IBM Cognos Disclosure Management 10.2.1 or later

Check IBM Support for IBM Cognos Disclosure Management security patches related to CVE-2013-0501
If a patch is available, download and apply it following IBM's installation instructions
Alternatively, upgrade to a newer version of IBM Cognos Disclosure Management (10.2.1 or later) that includes the fix
As a mitigation, disable the EdrawSoft EDOFFICE.EDOfficeCtrl.1 ActiveX control in Internet Explorer security settings
Ensure browsers are configured to prompt before running ActiveX controls or disable ActiveX entirely for untrusted zones

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

Fix this in Cognos Disclosure Management Scoped from the published advisory

Consultation4.0 h
Implementation6.0 h
Testing3.0 h
Review / QA2.0 h

15.0 hours of engineering $2,690

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-0501 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2013-0501?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 9.3 High

Exploit likelihood EPSS, next 30 days 1.5%

Affects: Cognos Disclosure Management

Remediation

A high-priority fix

Fix this in Cognos Disclosure Management 15 hrs · Moderate

Typical engagement from $2,690

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2013-0501 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References