CVE-2022-42122
CRITICALCVE-2022-42122 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in com.liferay.portal:release.portal.bom. O3 Security confirms whether CVE-2022-42122 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Liferay Portal and Liferay DXP Vulnerable to SQL Injection via Friendly URL Module
Real-World Exposure
com.liferay.portal:release.portal.bom☕com.liferay.portal:release.dxp.bom☕com.liferay:com.liferay.friendly.url.serviceReal-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
A SQL injection vulnerability in the Friendly Url module in Liferay Portal 7.3.7, and Liferay DXP 7.3 fix pack 2 through update 4 allows attackers to execute arbitrary SQL commands via a crafted payload injected into the title field of a friendly URL.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.liferay.portal:release.portal.bom | ≥ 7.3.7&&< 7.4.0-ga1 | 7.4.0-ga1 |
| ☕Maven | com.liferay.portal:release.dxp.bom | ≥ 7.3.10.fp2&&< 7.3.10.u4 | 7.3.10.u4 |
| ☕Maven | com.liferay:com.liferay.friendly.url.service | all versions | 4.0.3 |
Detection & 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update com.liferay.portal:release.portal.bom to 7.4.0-ga1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-42122 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2022-42122 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2022-42122. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2022-42122 in your dependencies?
O3 detects CVE-2022-42122 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.