CVE-2022-24697
CRITICALCVE-2022-24697 is a critical-severity (CVSS 9.8) OS Command Injection vulnerability in org.apache.kylin:kylin-core-common. O3 Security confirms whether CVE-2022-24697 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Apache Kylin prior to 4.0.2 allows command injection when the configuration overwrites function overwrites system parameters
Blast Radius
org.apache.kylin:kylin-core-common☕org.apache.kylin:kylin-spark-project☕org.apache.kylin:kylin-server-baseReal-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
Kylin's cube designer function has a command injection vulnerability when overwriting system parameters in the configuration overwrites menu. RCE can be implemented by closing the single quotation marks around the parameter value of “-- conf=” to inject any operating system command into the command line parameters. This vulnerability affects Kylin 2 version 2.6.5 and earlier, Kylin 3 version 3.1.2 and earlier, and Kylin 4 version 4.0.1 and earlier.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.kylin:kylin-core-common | all versions | 4.0.2 |
| ☕Maven | org.apache.kylin:kylin-spark-project | all versions | 4.0.2 |
| ☕Maven | org.apache.kylin:kylin-server-base | all versions | 4.0.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.kylin:kylin-core-common. 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 org.apache.kylin:kylin-core-common to 4.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24697 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-24697 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-24697. 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-24697 in your dependencies?
O3 detects CVE-2022-24697 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.