Version: Wowza Streaming Engine™ 4.9.1+2 build 20241119145805 released November 20, 2024.
Java support: Wowza Streaming Engine 4.9.1 is compiled using Java 17 (OpenJDK Java SE JRE 17.0.12) but can be used with Java versions 17 or 21. The Wowza Streaming Engine 4.9.1 installer and updater include a Java Runtime Environment (JRE) for Java 21 (OpenJDK Java SE JRE 21.0.3). During updates, we verify that Java 21 is present. If Java 21 isn't detected, the update is canceled, and you can install the JRE 21 provided with the updater before retrying the upgrade. You can manually roll back your Java version if needed. For more details, see Wowza Streaming Engine support for Java.
New features and functionality in Wowza Streaming Engine 4.9.1
Wowza Streaming Engine is a robust, customizable, and scalable media server software that powers reliable streaming of high-quality video and audio to any device, anywhere.
Wowza Streaming Engine 4.9.1 doesn't contain any new features or functionality. However, this is an important service release that includes various security patches and bug fixes to make Wowza Streaming Engine more robust and reliable. For more, see Detailed list of changes in Wowza Streaming Engine 4.9.1.
Installation and update considerations for Wowza Streaming Engine 4.9.1
If you're updating to Wowza Streaming Engine 4.9.1 from a base installation of Wowza Streaming Engine 4.9.0 or earlier, see Updating to Wowza Streaming Engine 4.9.0 and later.
Note: Wowza Streaming Engine 4.8.28 and later doesn't include an updater or installer for macOS.
When using the Wowza Streaming Engine 4.9.1 installer to add a new instance of Wowza Streaming Engine on Windows, you may need to install additional dependencies to ingest SRT MediaCaster streams or use the generic SRT stream targets destination to publish an SRT stream. For more information, see our Ingest and publish an SRT stream guide.
For step-by-step instructions on how to install or update Wowza Streaming Engine, see the following articles:
- Install – Install and configure Wowza Streaming Engine
- Update – Update your Wowza Streaming Engine installation
Breaking changes in Wowza Streaming Engine 4.9.1
Akamai stream targets
Akamai stream targets haven't yet been certified with Wowza Streaming Engine 4.9.0 - 4.9.1. If you're using Wowza Streaming Engine to send live streams to the Akamai HD network for distributed delivery, use a previous version of Wowza Streaming Engine.
Java version information
Wowza Streaming Engine 4.9.0 - 4.9.1 is officially certified, thoroughly tested, and optimized to run seamlessly with the Java 21 JRE. You get the following Java features:
- Installer details – Wowza Streaming Engine 4.9.0 - 4.9.1 is compiled using Java 17 (OpenJDK Java SE JRE 17.0.12), but new installations include a JRE for Java 21 (OpenJDK Java SE JRE 21.0.3). You can roll back to Java 17 if needed. Older Java versions (16 and below) are no longer supported and cannot be used with Wowza Streaming Engine 4.9.0 and later.
- Updater details – When using the updater for Wowza Streaming Engine 4.9.0 - 4.9.1, we verify that the Java 21 Virtual Machine (JVM) is present before completing the upgrade. If Java 21 isn't detected on the machine, the update is canceled with a message containing recommended steps. If you need a new version of Java, the updater includes JRE 21 with instructions explaining how to copy it from the root of the installer to the Wowza Streaming Engine installation folder. When you're updating to Wowza Streaming Engine 4.9.0 - 4.9.1 from a base installation of Wowza Streaming Engine 4.8.28 or earlier, check these considerations.
- Supported Java versions – If you prefer, you can manually install a different Java version. We support Java versions 17 or 21 with Wowza Streaming Engine 4.9.0 - 4.9.1.
While we tested Wowza Streaming Engine 4.8.28 - 4.9.1 with the Java 21 Runtime Environment (JRE), we didn't recompile it using Java Development Kit (JDK) 21. If you build a custom module using Java 21, it may not work with Wowza Streaming Engine if your source code includes Java 21 features.
Note: New installations of Wowza Streaming Engine 4.8.28 and later deliver generational support for the Z Garbage Collector (ZGC). To use Java 21 with Generational ZGC on Windows, you must be running a 64-bit version of Windows 10 (version 1803 or later) or Windows Server 2019 or later. You also need a 64-bit JVM.
If your Wowza Streaming Engine workflow uses custom modules or plugins, we suggest testing them with Wowza Streaming Engine 4.8.28 - 4.9.1 in a non-production environment before updating your media server software. The following Java modules are included with the JRE and installer for the Wowza Streaming Engine 4.8.28 - 4.9.1:
- java.base
- java.datatransfer
- java.desktop
- java.instrument
- java.logging
- java.management
- java.management.rmi
- java.naming
- java.prefs
- java.rmi
- java.scripting
- java.scripting.jgss
- java.security.sasl
- java.sql
- java.transaction.xa
- java.xml
- jdk.crypto.cryptoki
- jdk.crypto.ec
- jdk.httpserver
- jdk.management
- jdk.management.agent
- jdk.naming.rmi
- jdk.unsupported
- jdk.xml.dom
- jdk.attach (available with Wowza Streaming Engine 4.8.28 and later)
- jdk.internal.jvmstat (available with Wowza Streaming Engine 4.8.28 and later)
- jdk.jcmd (available with Wowza Streaming Engine 4.8.28 and later)
- jdk.jfr (available with Wowza Streaming Engine 4.8.28 and later)
- java.net.http (available with Wowza Streaming Engine 4.8.28 and later)
If you have other dependencies, you must install a Java 17 JRE or JDK for Wowza Streaming Engine 4.9.0 - 4.9.1 that includes these dependencies. For more information, see Manually install and troubleshoot Java on Wowza Streaming Engine.
You can also check the Wowza Streaming Engine support for Java page to learn more about the different Java versions we support.
Detailed list of changes in Wowza Streaming Engine 4.9.1
These changes were made since the release of Wowza Streaming Engine 4.9.0:
- Resolved CVE-2024-52052 RAPID7-WOWZA-WRITEJSP. We added various validations to confirm pushPublishMapPath values for custom application settings set via Wowza Streaming Engine Manager and the Wowza Streaming Engine REST API. These checks don't apply when directly editing the pushPublishMapPath property in the Application.xml configuration file. We confirm that:
- The pushPublishMapPath value is not empty and contains a TXT file extension.
- The pushPublishMapPath starts with the VHostConfigHome prefix and doesn't include a relative path.
- The pushPublishMapPath file can't be saved under the manager folder in the installation directory.
- Resolved CVE-2024-52053 RAPID7-WOWZA-XSS. We modified application logs to escape all text and prevent user-generated text from being rendered directly into HTML.
- Resolved CVE-2024-52054 RAPID7-WOWZA-TRAVERSAL-1. We added validation to check that application names created with the Wowza Streaming Engine REST API don't contain path traversal or various special characters.
- Resolved CVE-2024-52055 RAPID7-WOWZA-TRAVERSAL-2. We updated the Wowza Streaming Engine REST API to check source and destination application names for path traversal or special characters when an application is copied.
- Resolved CVE-2024-52056 RAPID7-WOWZA-TRAVERSAL-3. We added validation to the Wowza Streaming Engine REST API that checks an application name doesn't contain path traversal or special characters when an application is deleted.
- Upgraded the version of Spring Security to 6.2.7.
- Made changes in Wowza Streaming Engine Manager and the Wowza Streaming Engine REST API to ensure Name and Configuration Directory are read-only fields for the Virtual Host Setup page.
- Fixed an issue causing SRT stream connection failures due to null pointer exceptions when parsing description headers for certain encoders.
- Removed the netty-nio-client dependency to resolve an issue impacting AWS SDK API calls and the Media Cache workflow.
- Fixed an issue causing 403 errors when enabling multiple properties for HTTP Streamers Cupertino Settings in Wowza Streaming Engine Manager.
Known issues with Wowza Streaming Engine 4.9.1
For a detailed list of currently known issues, see Known issues with Wowza Streaming Engine.
