====== Security Update for Lime BI - Java Remote Code Execution Vulnerability (Java4Shell) ====== ===== Overview ===== A flaw in Java can let an attacker run code on a Lime BI server. Lime Cloud is already patched, so this concerns only on-premise installations. Until a fixed Java version is available, a Java option works around the flaw. ''lime-bi update'' with Lime BI 4.24.0 or later turns the workaround on, and new installations made with Lime BI 4.23.2 or later have it already. //When// a fixed Java version is released, ''lime-bi update'' installs it. * **Severity:** High * **Status:** Workaround available, fix pending * **Evidence of exploitation:** None observed * **Environment:** On-premise ===== Vulnerability Details ===== ==== What is affected? ==== Lime BI on-premise installations made with Lime BI 4.1.0 or later. These versions install Java 21. The flaw needs an Intel or AMD processor that supports AVX-512. A virtual machine may hide that support, so treat every server as affected. Installations made with Lime BI 4.0.x or earlier are not affected, because they run Java 11. ==== What is the risk? ==== Crafted Base64 data sent to Metabase can make Java read or write outside its memory, which can let an attacker read data or run code on the server. ==== Background ==== CVE-2026-114938, published by OpenJDK on November 17, 2026, affects Java 17 and later. Eclipse Temurin, the Java that Lime BI installs, has no fixed Java 21 version yet. ===== Solution ===== ^ Your installation ^ What to do ^ | Lime Cloud | Nothing. Lime Cloud is already patched. | | New installation | Install with Lime BI 4.24.0 or later. | | Made with Lime BI 4.23.2 or later | Nothing. The workaround is already on. | | Made with Lime BI 4.1.0-4.23.1 | Update with Lime BI 4.24.0 or later. If you can't, apply the registry workaround. | | Made with Lime BI 4.0.x or earlier | Nothing, because it runs Java 11. If you upgrade, use Lime BI 4.24.0 or later. | If you don't know which version made the installation, update with Lime BI 4.24.0 or later. It does no harm on an installation that already has the workaround. ==== Update with Lime BI 4.24.0 ==== - Run ''lime-bi update'' with Lime BI 4.24.0 or later on the server where Lime BI runs. - Confirm the update. ''lime-bi update'' stops the **Lime BI** service, updates it, and starts it again. - Check the workaround. ''lime-bi update'' sets the Java options and the environment variables of the **Lime BI** service to the ones that Lime ships. If the registry workaround was applied, ''lime-bi update'' replaces it with the same Java option in **Arguments**. ==== Check the Workaround ==== Run ''lime-bi nssm'' and look for ''-XX:-UseBASE64Intrinsics'' in **Arguments** on the **Application** tab. On a server that has only the registry workaround, ''C:\LimeBI\log.txt'' has the line ''Picked up JAVA_TOOL_OPTIONS: -XX:-UseBASE64Intrinsics'' instead. ==== Apply the Registry Workaround ==== Use the registry workaround only if you can't update with Lime BI 4.24.0 or later. - Download [[https://builds.lundalogik.com/api/v1/builds/lime-bi-java4shell/versions/1/file|lime-bi-java4shell-1.reg]] to the server where Lime BI runs. - Double-click the file and confirm. - Restart the **Lime BI** service in Windows Services. - Open ''C:\LimeBI\log.txt'' and check that it has the line ''Picked up JAVA_TOOL_OPTIONS: -XX:-UseBASE64Intrinsics''. ''lime-bi update'' with Lime BI 4.23.2 or earlier keeps the registry setting. ===== Recommendations ===== - **Update with Lime BI 4.24.0 or later now, so that the Java fix needs no new Lime BI release.** When a fixed Java version is released, Lime publishes it, and the next ''lime-bi update'' installs it and removes the workaround. A server with a [[https://lime-lime-bi.readthedocs-hosted.com/en/latest/updating-metabase/#how-do-i-schedule-updates|scheduled update]] gets the fix on its own. We will update this bulletin when the fix is released. - **Contact [[https://customer.lime-technologies.com/|Support]]** if you need help.