CVE-2024-54183
BaseFortify
Publication date: 2025-06-18
Last updated on: 2025-07-25
Assigner: IBM Corporation
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| ibm | sterling_b2b_integrator | From 6.0.0.0 (inc) to 6.1.2.7 (exc) |
| ibm | sterling_b2b_integrator | From 6.2 (inc) to 6.2.0.5 (exc) |
| ibm | sterling_file_gateway | From 6.0.0.0 (inc) to 6.1.2.7 (exc) |
| ibm | sterling_file_gateway | From 6.2.0.0 (inc) to 6.2.0.5 (exc) |
| ibm | aix | * |
| microsoft | windows | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2024-54183 is a cross-site scripting (XSS) vulnerability in the mailbox user interface of IBM Sterling B2B Integrator and IBM Sterling File Gateway versions 6.0.0.0 through 6.2.0.4. It allows an authenticated user to inject arbitrary JavaScript code into the web UI, which can alter the intended functionality of the interface and potentially lead to the disclosure of credentials within a trusted session. [1]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing an authenticated user to execute arbitrary JavaScript code in the web interface, potentially altering its intended functionality. This can lead to the disclosure of credentials within a trusted session, which may compromise user accounts and sensitive information. [1]
What immediate steps should I take to mitigate this vulnerability?
To mitigate the CVE-2024-54183 vulnerability, you should apply the fixes provided in APAR IT47515. Specifically, upgrade IBM Sterling B2B Integrator and IBM Sterling File Gateway to at least version 6.1.2.7, 6.2.0.5, or 6.2.1.0 depending on your current version. No workarounds or alternative mitigations are provided, so upgrading to the fixed versions is the recommended immediate step. [1]