There’s also JAVA_TOOL_OPTIONS, which you can set globally, but I personally never use it.
Unless you’re exposing Jenkins publicly, I wouldn’t worry too much about it. My understanding is that exploiting the vulnerability requires crafting a pretty targeted attack and I haven’t seen any reports of this being exploited at scale, even against publicly exposed services.
The best solution is to install the patched JDK once it’s available for your OS and JDK version. At least Temurin is taking their sweet time with it.
Setting JVM arguments for Jenkins depends on how it’s installed. For example, if it’s running as a systemd service, just add or modify:
[Service] Environment="JAVA_OPTS=-XX:-UseBASE64Intrinsics"There’s also
JAVA_TOOL_OPTIONS, which you can set globally, but I personally never use it.Unless you’re exposing Jenkins publicly, I wouldn’t worry too much about it. My understanding is that exploiting the vulnerability requires crafting a pretty targeted attack and I haven’t seen any reports of this being exploited at scale, even against publicly exposed services.