Vulnerability in Class Mediator (CVE-2024-6541)
Summary
Vulnerability in Class Mediator (CVE-2024-6541). Confidential information can be exposed externally. Exploitable via messageContext.
Original description
The description as published by the source.
The Class Mediator fails to correctly validate or sanitize messageContext properties when they are used to populate dynamic values. This allows authenticated users to potentially access or modify data across different system invocations that should be isolated.
This weakness can lead to the disclosure of sensitive information belonging to other users or the unintended modification of system data by authenticated users. The exact impact depends on how messageContext properties are utilized within the affected WSO2 products.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2024-6541 has been found in Class Mediator.
Attackers can target a specific entry point like messageContext over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Class Mediator CVE-2024-6541" on the vendor's site.
CVE-2024-6541 (Class Mediator) — CWE-20 / CVSS v3 6.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: messageContext
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in Class Mediator. Attackers reach the vulnerable code path via messageContext.
Check the vendor advisory for the affected versions of Class Mediator. Attack surface: messageContext.
Severity: Medium (CVSS 6.8/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Class Mediator を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web security.docs.wso2.com
- web nvd.nist.gov
- web security.docs.wso2.com
- web github.com