CVE-2024-41745
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 · uneditedIBM CICS TX Standard 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 · high confidenceIBM CICS TX Standard contains a reflected cross-site scripting (XSS) vulnerability in its Web UI. An unauthenticated attacker can inject malicious JavaScript code through vulnerable input points, which executes in the context of a trusted user session, potentially leading to session hijacking and credential disclosure.
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= 11.1.0.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify IBM CICS TX installationCheck for IBM CICS TX installation by searching for the product directory in standard locations such as /opt/ibm/cics_tx, C:\Program Files\IBM\CICS_TX, or consult your system's software inventory.Affected if IBM CICS TX is not installed on the system.
-
Determine installed versionRun the command to display the IBM CICS TX version, typically via 'cicsctx version' or by inspecting version files in the installation directory such as 'version.txt' or 'cics.properties'.Affected if The installed version is exactly 11.1.0.0.
-
Confirm Web UI is enabledCheck the IBM CICS TX configuration for Web UI status by inspecting configuration files like cicstx.xml or the CICS TX management interface settings for web console activation.Affected if The Web UI (web console) is enabled and accessible.
-
Assess Web UI network exposureReview network configuration to determine if the CICS TX Web UI port is exposed to network-accessible interfaces rather than localhost only.Affected if The Web UI is reachable from network locations rather than restricted to local access only.
If IBM CICS TX version 11.1.0.0 is installed with its Web UI enabled and network-accessible, the environment is affected by this reflected XSS vulnerability.
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 dataApply IBM's security patch for CVE-2024-41745 immediately. Implement robust input validation and output encoding on all user-supplied data in the Web UI, and consider deploying Content Security Policy (CSP) headers to mitigate XSS execution.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-41745 — 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-2024-41745 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