CVE-2024-4598
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 · uneditedAn information disclosure vulnerability exists in multiple WSO2 products due to improper implementation of the enrich mediator. Authenticated users may be able to view unintended business data from other mediation contexts because the internal state is not properly isolated or cleared between executions. This vulnerability does not impact user credentials or access tokens but may lead to leakage of sensitive business information handled during message flows.
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 confidenceThis is an information disclosure vulnerability in WSO2's enrich mediator where internal state (business data in mediation contexts) is not properly isolated or cleared between executions. Authenticated users can potentially view sensitive business data from other users' mediation flows due to improper context isolation.
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>= 3.2.0, < 3.2.0.422>= 3.2.1, < 3.2.1.42>= 4.1.0, < 4.1.0.152>= 4.3.0, < 4.3.0.55>= 1.2.0, < 1.2.0.157>= 4.1.0, < 4.1.0.95CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Identify WSO2 product and versionLocate the version file in the WSO2 installation directory. For API Manager, check <install_dir>/repository/components/plugins for the core jar or examine the management console's About page. For Micro Integrator, check <install_dir>/wso2mi/version.txt or the wrapper.conf file.Affected if The installed version falls within any of these ranges: WSO2 API Manager 3.2.0 to 3.2.0.421, 3.2.1 to 3.2.1.41, 4.1.0 to 4.1.0.151, or 4.3.0 to 4.3.0.54; WSO2 Micro Integrator 1.2.0 to 1.2.0.156 or 4.1.0 to 4.1.0.94.
-
Locate enrich mediator usage in mediation configurationsSearch for 'enrich' mediator elements in all synapse configuration files within the <install_dir>/repository/deployment/server/synapse-configs/default/ directory. Check all sequences, proxy services, and API definitions for <enrich> tags.Affected if The enrich mediator is actively configured in any mediation flow (sequence, proxy service, or API).
-
Verify multi-user or multi-tenant environmentReview the deployment to determine if multiple authenticated users or tenants have access to execute mediation flows. Check user roles, tenant configurations, and whether shared sequences or endpoints are used.Affected if More than one authenticated user or multiple tenants share access to the same mediation runtime where enrich mediator sequences are deployed.
-
Inspect mediation context handlingExamine logs and test for data leakage between different user sessions by executing enrich mediator flows with different user credentials and observing if response data contains information from other user contexts.Affected if Mediation flow outputs contain data from other users' execution contexts, indicating improper context isolation.
You are affected if you run a vulnerable WSO2 version AND use the enrich mediator in mediation flows within a multi-user or multi-tenant environment where context data could leak between users.
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.
dbcve · scoped1.2.0.1573.2.0.4223.2.1.42
Apply vendor-provided patches for the enrich mediator to ensure proper state isolation between mediation contexts. Review and test existing mediation flows for any unintended data exposure.
WSO2 Api Manager 3.2.0.422+, 3.2.1.42+, 4.1.0.152+, or 4.3.0.55+ | WSO2 Micro Integrator 1.2.0.157+ or 4.1.0.95+
- 1. Identify the currently deployed WSO2 product (Api Manager or Micro Integrator) and its exact version from the affected version ranges.
- 2. For WSO2 Api Manager: upgrade to version 3.2.0.422 or later (if on 3.2.x branch), or 3.2.1.42 or later (if on 3.2.1 branch), or 4.1.0.152 or later (if on 4.1.0 branch), or 4.3.0.55 or later (if on 4.3.0 branch).
- 3. For WSO2 Micro Integrator: upgrade to version 1.2.0.157 or later (if on 1.2.0 branch) or 4.1.0.95 or later (if on 4.1.0 branch).
- 4. After upgrading, test mediation workflows that utilize the enrich mediator to ensure proper functionality.
- 5. Verify that the enrichment mediator now properly isolates internal state between mediation context executions.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4598 — 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-4598 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