CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2024-1132 remediation guide

Red Hat Migration Toolkit for Runtimes 1 on RHEL 8, MTA-6.2-RHEL-9, Red Hat AMQ Broker 7

A flaw was found in Keycloak, where it does not properly validate URLs included in a redirect. This issue could allow an attacker to construct a malicious request to bypass validation and access other URLs and sensitive information within the domain or conduct further attacks. This flaw affects any client that utilizes a wildcard in the Valid Redirect URIs field, and requires user interaction within the malicious URL.

Open CVE record
ProductRed Hat Migration Toolkit for Runtimes 1 on RHEL 8, MTA-6.2-RHEL-9, Red Hat AMQ Broker 7
Affected versions>= 21.1.0 < 22.0.10, >= 23.0.0 < 24.0.3, 1.0, 4.11, 4.12, 4.9, 4.10, 7.6
Fixed versions22.0.10, 24.0.3
Priority basisReview · CVSS 8.1 · EPSS 1.55%
01

Identify the affected asset

Confirm whether Red Hat Migration Toolkit for Runtimes 1 on RHEL 8, MTA-6.2-RHEL-9, Red Hat AMQ Broker 7 is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= 21.1.0 < 22.0.10, >= 23.0.0 < 24.0.3, 1.0, 4.11, 4.12, 4.9, 4.10, 7.6. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 22.0.10, 24.0.3. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.