dbcve.org
Tivoli Application Dependency Discovery ManagerApplication · Ibm

CVE-2014-6149

MEDIUM · 5.0 CVSS v2.0 Published 2014-10-29
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
Directory traversal vulnerability in BIRT-viewer in IBM Tivoli Application Dependency Discovery Manager (TADDM) 7.2.0.0 through 7.2.0.10, 7.2.1.0 through 7.2.1.6, and 7.2.2.0 through 7.2.2.2 allows remote authenticated users to read arbitrary files via unspecified 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

Directory traversal vulnerability in the BIRT-viewer component of IBM TADDM allows authenticated remote users to access arbitrary files on the server by manipulating file paths with '..' sequences or absolute paths, bypassing intended access restrictions in the web application.

MitigationApply the vendor-supplied patches for IBM TADDM versions 7.2.0.0-7.2.0.10, 7.2.1.0-7.2.1.6, and 7.2.2.0-7.2.2.2 to remediate the directory traversal vulnerability in BIRT-viewer. As a compensating control, restrict network access to the BIRT-viewer to authorized personnel only.

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
Tivoli Application Dependency Discovery ManagerApplication
Affected:= 7.2.0= 7.2.0.1= 7.2.0.2= 7.2.0.3= 7.2.0.4= 7.2.0.5= 7.2.0.6= 7.2.0.7= 7.2.0.8= 7.2.0.9= 7.2.0.10= 7.2.1

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 IBM TADDM installation and version
    Locate the TADDM installation directory and check the version file, typically found in the installation root or via the ' colchk' command or version.info file
    Affected if The installed version matches 7.2.0.x (any point release from 7.2.0 through 7.2.0.10) or 7.2.1.x (any point release) since these are the affected versions listed in the CVE
  2. Locate the BIRT-viewer component
    Navigate to the BIRT-viewer web application directory within the TADDM installation, typically under the 'webapps' or 'taddmweb' directory, and identify the 'viewer' subdirectory
    Affected if The BIRT-viewer component exists and is deployed on the server, as this is the vulnerable component
  3. Check BIRT-viewer accessibility
    Verify if the BIRT-viewer web application is accessible over the network by accessing the URL pattern: http://<server>:9080/<context>/viewer/ or checking the deployed web.xml configuration
    Affected if The BIRT-viewer is accessible via HTTP/HTTPS without additional authentication barriers beyond basic authentication, as the vulnerability allows authenticated users to bypass restrictions
  4. Test for directory traversal vulnerability
    If you have authenticated access, attempt a controlled test request using '..' sequences in the 'filename' parameter of the BIRT-viewer URL (e.g., /viewer/frameset?__report=test.rptdesign&filename=../../../../../../etc/passwd) to see if arbitrary file access is possible
    Affected if The request returns file contents outside the intended BIRT-viewer directories, confirming the directory traversal vulnerability is present

If IBM TADDM version 7.2.0.x or 7.2.1.x is installed AND the BIRT-viewer component is accessible over the network, the environment is likely affected by this directory traversal vulnerability.

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 vendor-supplied patches for IBM TADDM versions 7.2.0.0-7.2.0.10, 7.2.1.0-7.2.1.6, and 7.2.2.0-7.2.2.2 to remediate the directory traversal vulnerability in BIRT-viewer. As a compensating control, restrict network access to the BIRT-viewer to authorized personnel only.

Fix this in Tivoli Application Dependency Discovery Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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