CVE REMEDIATION GUIDE
CISA KEV · Known exploitedCriticalFixed-version data available

CVE-2022-24112 remediation guide

Apache APISIX

An attacker can abuse the batch-requests plugin to send requests to bypass the IP restriction of Admin API. A default configuration of Apache APISIX (with default API key) is vulnerable to remote code execution. When the admin key was changed or the port of Admin API was changed to a port different from the data panel, the impact is lower. But there is still a risk to bypass the IP restriction of Apache APISIX's data panel. There is a check in the batch-requests plugin which overrides the client IP with its real remote IP. But due to a bug in the code, this check can be bypassed.

Open CVE record
ProductApache APISIX
Affected versionsApache APISIX 2.12, Apache APISIX 2.10, 1.3, < 2.10.4, >= 2.11.0 < 2.12.1
Fixed versions2.10.4, 2.12.1
Priority basisImmediate · CVSS 9.8 · EPSS 96.0%
01

Identify the affected asset

Confirm whether Apache APISIX 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: Apache APISIX 2.12, Apache APISIX 2.10, 1.3, < 2.10.4, >= 2.11.0 < 2.12.1. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Apply updates per vendor instructions.

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.