dbcve.org
Jazz For Service ManagementApplication · Ibm

CVE-2024-52892

MEDIUM · 6.1 CVSS v3.1 Published 2025-02-06
Fix available
A fix is available. Upgrade to 1.1.3.24 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Jazz for Service Management 1.1.3 through 1.1.3.23 is vulnerable to cross-site scripting. This vulnerability allows an unauthenticated attacker to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.

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

Stored cross-site scripting vulnerability in IBM Jazz for Service Management versions 1.1.3 through 1.1.3.23 allows unauthenticated attackers to inject arbitrary JavaScript into the Web UI, which executes within legitimate user sessions and can lead to credential theft.

MitigationApply IBM's fix (upgrade to version 1.1.3.24 or later, or apply the provided patch) and validate that input sanitization is properly enforced.

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
Jazz For Service ManagementApplication
Affected:>= 1.1.3, < 1.1.3.24

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 Jazz for Service Management version
    Locate the product installation directory and check version files, or access the administrative console and view the system information/About section
    Affected if Installed version is 1.1.3 through 1.1.3.23 (any version >= 1.1.3 but < 1.1.3.24)
  2. Confirm Web UI is accessible
    Verify that the IBM Jazz for Service Management web interface is exposed and reachable via browser at the configured endpoint
    Affected if Web UI is exposed and accessible to unauthenticated or authenticated users
  3. Review recent UI input submissions
    Inspect application logs or database records for user-generated content in Web UI fields (forms, search parameters, user profile fields) for any suspicious script tags or unexpected HTML/JavaScript
    Affected if Arbitrary script tags or JavaScript code are found stored in user-controllable UI fields
  4. Check for unauthorized session activity
    Review Web UI access logs and user session records for unexpected JavaScript execution patterns or credential access attempts
    Affected if Logs show script execution in user contexts or unauthorized actions performed via injected scripts

Your environment is affected if IBM Jazz for Service Management version is 1.1.3.x where x < 24 and the Web UI is accessible to users.

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 1.1.3.24 or later
Fixed in 1.1.3.24
Interim mitigation

Apply IBM's fix (upgrade to version 1.1.3.24 or later, or apply the provided patch) and validate that input sanitization is properly enforced.

Recommended fix High confidence

Jazz for Service Management 1.1.3.24

  1. Verify the current installed version of Jazz for Service Management using the administration console or version check command
  2. Download Jazz for Service Management version 1.1.3.24 or later from IBM Fix Central or the IBM Jazz for Service Management support portal
  3. Review the IBM installation and upgrade documentation for Jazz for Service Management
  4. Stop all Jazz for Service Management services and applications before proceeding with the upgrade
  5. Perform a full backup of the existing Jazz for Service Management database and configuration files
  6. Run the upgrade installer for version 1.1.3.24 following the documented upgrade procedure
  7. After upgrade completion, verify all services start successfully
  8. Log in to the Web UI and verify the application is functioning correctly

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

Fix this in Jazz For Service Management Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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