dbcve.org
Analytics Content HubApplication · Ibm

CVE-2024-38327

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-10
Fix available
A fix is available. Upgrade to 2.4 or later.
See remediation →
100/100
Remediation priority · Urgent
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, 2.1, 2.2, and 2.3 is vulnerable to information exposure and further attacks due to an exposed JavaScript source map which could assist an attacker to read and debug JavaScript used in the application's API.

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 versions 2.0-2.3 exposes JavaScript source map (.map) files in production. These files map minified JavaScript back to original source code, revealing API endpoint structures, application logic, variable names, and internal implementation details that assist attackers in reconnaissance and developing further exploits.

MitigationRemove all .map files from production deployments or configure the web server to deny HTTP requests for source map files. Alternatively, ensure source maps are not included in production builds.

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.4

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 Analytics Content Hub version
    Check the installed version through the product's admin interface, about page, or installation metadata. Look for version 2.0 through 2.3.x.
    Affected if The installed version is 2.0, 2.0.x, 2.1, 2.1.x, 2.2, 2.2.x, 2.3, or 2.3.x.
  2. Check for accessible .map files via HTTP
    Use a web browser or curl command to attempt accessing common .map file URLs on the Content Hub domain, such as /static/*.js.map or similar paths where JavaScript files are hosted.
    Affected if HTTP requests for .map files return 200 OK responses instead of 403 Forbidden or 404 Not Found.
  3. Enumerate web root for .map file references
    Spider or crawl the production web application and capture all HTTP responses. Search the captured traffic for any URLs ending in .map extension.
    Affected if Any .map files are found being served via HTTP to clients.
  4. Review web server configuration for .map handling
    Inspect the web server configuration (IBM HTTP Server, nginx, Apache, etc.) serving Content Hub. Look for rules that explicitly allow or fail to block .map file requests.
    Affected if The web server configuration lacks rules to deny .map file requests.

You are affected if the installed IBM Analytics Content Hub version is 2.0 through 2.3.x AND .map files are accessible via HTTP on the production site.

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.4 or later
Fixed in 2.4
Interim mitigation

Remove all .map files from production deployments or configure the web server to deny HTTP requests for source map files. Alternatively, ensure source maps are not included in production builds.

Recommended fix High confidence

2.4

  1. Download IBM Analytics Content Hub version 2.4 or later from IBM's official support portal
  2. Review the IBM Analytics Content Hub 2.4 release notes and upgrade documentation
  3. Back up the current installation including all data and configurations
  4. Execute the upgrade procedure following IBM's documented upgrade path for version 2.4
  5. After upgrading, verify the vulnerability is resolved by confirming that .map files are no longer accessible via the web application's API endpoints
Caveat Review IBM's release notes for version 2.4 to check for any breaking changes, deprecated features, or migration requirements 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
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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