CVE-2013-2974
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 · uneditedThe BIRT viewer in IBM Tivoli Application Dependency Discovery Manager (TADDM) 7.2.1.x before 7.2.1.5 allows remote authenticated users to bypass authorization checks and obtain report-administration privileges, and consequently create or delete reports or conduct SQL injection attacks, via crafted parameters to the BIRT reporting URL.
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 confidenceThe BIRT viewer in IBM TADDM 7.2.1.x before 7.2.1.5 contains an authorization bypass vulnerability where crafted parameters to BIRT reporting URLs allow authenticated users to bypass normal authorization checks and obtain report-administration privileges. This enables attackers to create/delete reports and potentially conduct SQL injection attacks.
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= 7.2.1.1= 7.2.1.2= 7.2.1.3= 7.2.1.4CVSS 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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if IBM TADDM is installedLook for the TADDM installation directory (commonly under /opt/IBM/TADDM or C:\IBM\TADDM on Windows), or check for running processes named 'collation' or 'taddm'Affected if IBM TADDM software is present on the system
-
Determine the installed TADDM versionCheck the version file in the TADDM installation directory, typically at <TADDM_HOME>/etc/collation.version or use the 'collgthlp -version' command from the TADDM bin directoryAffected if The version is 7.2.1.1, 7.2.1.2, 7.2.1.3, or 7.2.1.4
-
Check if BIRT viewer web component is accessibleAccess the TADDM web interface and navigate to the BIRT viewer URL pattern (typically /taddm/reporting or /BIRT), or check web configuration files in <TADDM_HOME>/dist\logs\collation\web\ for BIRT-related servlet mappingsAffected if BIRT viewer web component is enabled and accessible
-
Review web access logs for suspicious BIRT URL patternsExamine web server access logs (in <TADDM_HOME>/dist\logs\collation\logs\) for BIRT reporting URLs containing unusual parameters that could indicate exploitation attempts, such as abnormal privilege escalation patternsAffected if BIRT viewer logs show unusual or unauthorized report administration requests
A system is affected if IBM TADDM version 7.2.1.1 through 7.2.1.4 is installed with the BIRT viewer component enabled and accessible.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade IBM TADDM to version 7.2.1.5 or later to obtain the vendor patch that addresses this authorization bypass in the BIRT viewer.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2974 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-2974 in production — separate from our analysis above.
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.
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.
- 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