News

“Java4Shell” and verinice

A security vulnerability in the Java Runtime Environment has been disclosed under the name “Java4Shell” (see report on Heise Security). The vulnerability occurs exclusively in conjunction with certain CPU models. Depending on the hardware in use, locally operated verinice environments may also be affected.

We have reviewed our product lines (verinice.cloud, verinice.onprem, verinice.PRO, and the verinice single-user version) and will provide ongoing updates here regarding the current status and recommended actions.

1. verinice.cloud

  • Status: Not affected
  • Background: The infrastructure provided by our hosting partner SysEleven for verinice.cloud does not use any of the CPUs affected by this security vulnerability. Users of verinice.cloud do not need to take any action.

2. verinice.onprem (Kubernetes helm chart & virtual appliance)

  • Status: Depending on the customer's setup (hardware used)
  • Risk Assessment: Since verinice.onprem is typically operated within secure, internal corporate networks, an attack from outside is already significantly more difficult. Nevertheless, we recommend that all customers running verinice.onprem on affected hardware actively prevent exploitation of this vulnerability by adjusting the Helm configuration.
  • Implementation (when using the latest version of Helm Charts):
    Add the following Java options to your myValues.yaml (virtual appliance) or values.yaml (Kubernetes cluster) to disable the affected Base64 intrinsics:
keycloak:
  embedded:
    workload:
      extraEnv:
        JAVA_OPTS_APPEND: "-XX:-UseBASE64Intrinsics"

service:
  veo:
    additionalJavaOpts: "-XX:MaxRAMPercentage=70.0 -Djdk.serialFilter=maxbytes=0 -XX:-UseBASE64Intrinsics"
  history:
    additionalJavaOpts: "-XX:MaxRAMPercentage=70.0 -XX:-UseBASE64Intrinsics"
  reporting:
    additionalJavaOpts: "-XX:MaxRAMPercentage=70.0 -XX:-UseBASE64Intrinsics"
  accounts:
    configmap:
      additionalJavaOpts: "-XX:MaxRAMPercentage=70.0 -XX:-UseBASE64Intrinsics"
  forms:
    configmap:
      additionalJavaOpts: "-XX:MaxRAMPercentage=70.0 -XX:-UseBASE64Intrinsics"

 

Configuration Notes:

  • If “accounts” and ‘forms’ are defined at the top level (outside of “service:”) in your Chart version, set the entries accordingly under “accounts.configmap.additionalJavaOpts” or “forms.configmap.additionalJavaOpts.”
  • If you have connected your own external Keycloak instance instead of the included Keycloak (keycloak.embedded), please also check the hardware and JVM configuration used there.
  • Then update your deployment as usual using Helm (e.g., `helm upgrade -n veo -f myValues.yaml verinice-onprem oci://registry.verinice.com/sernet/veriniceveo/veo --force-conflicts`).

3. verinice.PRO (Server & Client) and the verinice single-user version

  • Status: Depending on the customer's setup (hardware used)
  • Risk Assessment: Here, too, while the fact that the system is typically operated within a company significantly reduces the likelihood of an attack, it does not completely rule out the possibility of exploitation on affected hardware within the internal network.
  • verinice.PRO Server: Updates to the Java Runtime Environment are generally performed as part of regular system maintenance by your own IT administration team as soon as your operating system vendor releases the corresponding updates. We are currently coordinating internally to determine any additional recommendations regarding the exact procedure.
  • verinice.PRO Client & verinice Single-user version: We are currently reviewing the exact procedure.

As soon as the technical testing for verinice.PRO and the verinice single-user version is complete, we will update this page and provide information on the specific steps to take.

If you have any questions, our support team will be happy to assist you at support@verinice.com.

4. P.S.: The nginx vulnerability

On the evening of November 18, 2026, a vulnerability was reported in the “nginx” webserver. verinice is not affected by this in any way.

Contact us
Contact