Chapter 5. Fixed issues
The following sections list the issues fixed in AMQ Streams 1.6.x. Red Hat recommends that you upgrade to the latest patch release if you are using AMQ Streams 1.6.x with OpenShift Container Platform 3.11
For details of the issues fixed in:
- Kafka 2.6.3, refer to the Kafka 2.6.3 Release Notes
- Kafka 2.6.2, refer to the Kafka 2.6.2 Release Notes
- Kafka 2.6.1, refer to the Kafka 2.6.1 Release Notes
- Kafka 2.6.0, refer to the Kafka 2.6.0 Release Notes
5.1. Fixed issues for AMQ Streams 1.6.7 Copy linkLink copied to clipboard!
The AMQ Streams 1.6.7 patch release (Long Term Support) is now available.
AMQ Streams 1.6.7 is the latest Long Term Support release for use with OpenShift Container Platform 3.11 only, and is supported only for as long as OpenShift Container Platform 3.11 is supported.
Note that AMQ Streams 1.6.7 is supported on OCP 3.11 only.
The AMQ Streams product images have been upgraded to version 1.6.7.
For additional details about the issues resolved in AMQ Streams 1.6.7, see AMQ Streams 1.6.x Resolved Issues.
Log4j vulnerabilities
AMQ Streams includes log4j 1.2.17. The release fixes a number of log4j vulnerabilities.
For more information on the vulnerabilities addressed in this release, see the following CVE articles:
5.2. Fixed issues for AMQ Streams 1.6.6 Copy linkLink copied to clipboard!
For additional details about the issues resolved in AMQ Streams 1.6.6, see AMQ Streams 1.6.x Resolved Issues.
Log4j2 vulnerabilities
AMQ Streams includes log4j2 2.17.1. The release fixes a number of log4j2 vulnerabilities.
For more information on the vulnerabilities addressed in this release, see the following CVE articles:
5.3. Fixed issues for AMQ Streams 1.6.5 Copy linkLink copied to clipboard!
For additional details about the issues resolved in AMQ Streams 1.6.5, see AMQ Streams 1.6.x Resolved Issues.
Log4j2 vulnerability
The 1.6.5 release fixes a remote code execution vulnerability for AMQ Streams components that use log4j2. The vulnerability could allow a remote code execution on the server if the system logs a string value from an unauthorized source. This affects log4j versions between 2.0 and 2.14.1.
For more information, see CVE-2021-44228.
5.4. Fixed issues for AMQ Streams 1.6.4 Copy linkLink copied to clipboard!
For additional details about the issues resolved in AMQ Streams 1.6.4, see AMQ Streams 1.6.x Resolved Issues.
5.5. Fixed issues for AMQ Streams 1.6.2 Copy linkLink copied to clipboard!
The AMQ Streams 1.6.2 patch release is now available. The release includes a number fixes related to Kafka Connect.
The AMQ Streams product images have not changed and remain at version 1.6.
For additional details about the issues resolved in AMQ Streams 1.6.2, see AMQ Streams 1.6.2 Resolved Issues.
Following a CVE update, the version of AMQ Streams managed by the Operator Lifecycle Manager (OLM) was changed to 1.6.1. To avoid confusion, the patch release for AMQ Streams 1.6 was given a version number of 1.6.2.
5.6. Fixed issues for AMQ Streams 1.6.0 Copy linkLink copied to clipboard!
| Issue Number | Description |
|---|---|
| Kafka Bridge: Kafka consumer should be tracked with group-consumerid key | |
| Allow downgrade with message version older than the downgrade version | |
| Diff PodDisruptionBudgets before patching them to not recreate them on every reconciliation | |
| MirrorMaker 2 on OCP doesn’t properly mirror messages with headers | |
| MirrorMaker 2 doesn’t properly configure Jaeger tracing in the connectors | |
| When set to blank value for toleration Kafka cluster keeps rolling updates repeatedly | |
| Zookeeper version on the docs doesn’t match with the version in AMQ Streams 1.5 | |
| Connection Leak in Operator when Using KafkaConnect API | |
| Fix Secrets or ConfigMaps with dots mounted into Connect | |
| OLM install - yaml contains typo for 'authentication' |
| Issue Number | Description |
|---|---|
| CVE-2020-13956 httpclient: apache-httpclient: incorrect handling of malformed authority component in request URIs [amq-st-1] |