dbcve.org
Analytics Content HubApplication · Ibm

CVE-2024-35134

MEDIUM · 5.3 CVSS v3.1 Published 2025-01-25
Fix available
A fix is available. Upgrade to 2.3 or later.
See remediation →
62/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 Analytics Content Hub 2.0 could allow a remote attacker to obtain sensitive information when a detailed technical error message is returned in the browser. This information could be used in further attacks against the system.

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 Analytics Content Hub 2.0 returns detailed technical error messages (potentially including stack traces, file paths, or system configuration details) directly in browser responses, allowing unauthenticated remote attackers to gather sensitive system information for use in further attacks.

MitigationConfigure the application server to disable verbose error messages in production environments and display generic error pages to end users while logging detailed errors server-side for diagnostic purposes.

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
Analytics Content HubApplication
Affected:>= 2.0, < 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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 the installed IBM Analytics Content Hub version
    Access the IBM Analytics Content Hub admin console or about page, typically at /ibm/analytics-content-hub-admin/about or check the installation directory for version files. Alternatively, inspect the response headers or login page for version information.
    Affected if The version is 2.0, 2.1, or 2.2 (any version >= 2.0 but < 2.3)
  2. Trigger a test error condition
    Send a malformed or invalid request to the application, such as providing invalid parameters to an API endpoint, accessing a non-existent resource, or submitting malformed input to a form.
    Affected if The application returns detailed error messages including stack traces, file paths, Java class names, or system configuration details in the HTTP response body or error page
  3. Inspect HTTP error responses for information disclosure
    Use a browser developer tool or HTTP client (curl, burp) to capture the full response when the application encounters an error. Examine both the response body and any stack trace fragments.
    Affected if The error page or response contains technical details such as Java stack traces, absolute file paths, server configuration parameters, or internal system information instead of a generic error message

Your environment is affected if you are running IBM Analytics Content Hub versions 2.0 through 2.2 and the application returns detailed technical error messages (stack traces, file paths, or system details) in HTTP responses to invalid requests.

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
Upgrade available Upgrade to 2.3 or later
Fixed in 2.3
Interim mitigation

Configure the application server to disable verbose error messages in production environments and display generic error pages to end users while logging detailed errors server-side for diagnostic purposes.

Recommended fix Moderate confidence

Analytics Content Hub 2.3 or later

  1. 1. Back up your current IBM Analytics Content Hub installation and database
  2. 2. Review IBM's official documentation for Analytics Content Hub upgrade procedures
  3. 3. Plan for downtime required to perform the upgrade
  4. 4. Execute the upgrade to Analytics Content Hub version 2.3 or later
  5. 5. After upgrade, verify that error messages no longer expose detailed technical information in the browser
  6. 6. Test core functionality to ensure the upgrade did not introduce regressions
Caveat Review IBM's release notes for version 2.3 to check for any breaking changes or required migration steps before upgrading

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

Fix this in Analytics Content Hub Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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