CVE-2024-38002 — release.portal.bom
HIGHCVE-2024-38002 is a high-severity (CVSS 8.8) CWE-862 vulnerability in com.liferay.portal:release.portal.bom. A fix is available for com.liferay.portal:release.portal.bom — see the affected versions and patch details below.
Liferay Portal and Liferay DXP Workflow Component Does Not Check User Permissions
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-38002.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
com.liferay.portal:release.portal.bom☕com.liferay.portal:release.dxp.bom☕com.liferay.portal:release.dxp.bom☕com.liferay.portal:release.dxp.bom☕com.liferay.portal:release.dxp.bomReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
The workflow component in Liferay Portal 7.3.2 through 7.4.3.111, and Liferay DXP 2023.Q4.0 through 2023.Q4.5, 2023.Q3.1 through 2023.Q3.8, 7.4 GA through update 92 and 7.3 GA through update 36 does not properly check user permissions before updating a workflow definition, which allows remote non-authenticated users to modify workflow definitions and execute arbitrary code (RCE) via the headless API.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.liferay.portal:release.portal.bom | ≥ 7.3.2-ga3&&< 7.4.3.112-ga112 | 7.4.3.112-ga112com.liferay.portal:release.portal.bom:7.4.3.112-ga112 |
| ☕Maven | com.liferay.portal:release.dxp.bom | ≥ 2023.Q4.0&&< 2023.Q4.6 | 2023.Q4.6com.liferay.portal:release.dxp.bom:2023.Q4.6 |
| ☕Maven | com.liferay.portal:release.dxp.bom | ≥ 2023.Q3.1&&< 2023.Q3.9 | 2023.Q3.9com.liferay.portal:release.dxp.bom:2023.Q3.9 |
| ☕Maven | com.liferay.portal:release.dxp.bom | ≥ 7.3-ga&&< 7.3.10.u36 | 7.3.10.u36com.liferay.portal:release.dxp.bom:7.3.10.u36 |
| ☕Maven | com.liferay.portal:release.dxp.bom | ≥ 7.4-ga&&< 7.4.13.u92 | 7.4.13.u92com.liferay.portal:release.dxp.bom:7.4.13.u92 |
Affected Products
digital experience platformliferayliferay portalliferayDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.liferay.portal:release.portal.bom, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.liferay.portal:release.portal.bom to 7.4.3.112-ga112 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-38002 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2024-38002 in your dependencies?
Find it across Maven, including transitive dependencies.