CVE-2022-37434 remediation guide

CADRA, RUGGEDCOM ROX MX5000

zlib through 1.2.12 has a heap-based buffer over-read or buffer overflow in inflate in inflate.c via a large gzip header extra field. NOTE: only applications that call inflateGetHeader are affected. Some common applications bundle the affected zlib source code but may be unable to call inflateGetHeader (e.g., see the nodejs/node reference).

Open CVE record

ProductCADRA, RUGGEDCOM ROX MX5000

Affected versions< V2511, < V2.17.0, >= V3.1.0 < V3.1.5, <= 1.2.12, 35, 36, 37, 10.0, < 15.7.1, >= 16.0 < 16.1, >= 11.0 < 11.7.1, >= 12.0.0 < 12.6.1, < 9.1, >= 3.7.31 < 3.7.34, >= 3.11.0 < 3.11.22, >= 4.3.0 < 4.3.16, >= 4.6.0 < 4.6.3

Fixed versions15.7.1, 16.1, 11.7.1, 12.6.1, 9.1, 3.7.34, 3.11.22, 4.3.16, 4.6.3

Priority basisPriority · CVSS 9.8 · EPSS 17.9%

Identify the affected asset

Confirm whether CADRA, RUGGEDCOM ROX MX5000 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.

Validate the affected-version match

Compare the deployed version with the affected range: < V2511, < V2.17.0, >= V3.1.0 < V3.1.5, <= 1.2.12, 35, 36, 37, 10.0, < 15.7.1, >= 16.0 < 16.1, >= 11.0 < 11.7.1, >= 12.0.0 < 12.6.1, < 9.1, >= 3.7.31 < 3.7.34, >= 3.11.0 < 3.11.22, >= 4.3.0 < 4.3.16, >= 4.6.0 < 4.6.3. Treat incomplete inventory results as unresolved.

Prioritize with independent signals

FIRST EPSS indicates an elevated probability of exploitation. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 15.7.1, 16.1, 11.7.1, 12.6.1, 9.1, 3.7.34, 3.11.22, 4.3.16, 4.6.3. Preserve configuration and rollback material before change.

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.