dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 15 Sep 2022.
ApisixApplication · Apache

CVE-2022-24112

CRITICAL · 9.8 CVSS v3.1 Published 2022-02-11
Fix available
A fix is available. Upgrade to 2.10.4 / 2.12.1 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache APISIX's batch-requests plugin contains a vulnerability allowing attackers to bypass IP restrictions on the Admin API. The plugin has a check meant to override client IP with the real remote IP, but a bug in this check can be exploited. With default configurations (default API key), this enables remote code execution. Even when the admin key is changed or Admin API port differs from the data panel, the IP restriction bypass still poses risk to the data panel.

MitigationUpgrade Apache APISIX to the patched version. If immediate patching is not possible, disable or restrict the batch-requests plugin and ensure Admin API is not exposed to untrusted networks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ApisixApplication
Affected:< 2.10.4>= 2.11.0, < 2.12.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Apache APISIX version
    Run 'apisix version' or check the version in conf/config.yaml. Compare against affected ranges: < 2.10.4 or >= 2.11.0 and < 2.12.1
    Affected if Installed version falls within the affected ranges
  2. Verify batch-requests plugin is enabled
    Check conf/config.yaml under plugins list, or query the /apisix/admin/plugins endpoint using the Admin API
    Affected if batch-requests appears in the enabled plugins list
  3. Check if Admin API is network accessible
    Review network configuration and firewall rules to determine if port 9080 (default Admin API HTTP port) or 9443 (HTTPS) is exposed to untrusted networks
    Affected if Admin API port is reachable from untrusted/external networks
  4. Confirm default API key is still in use
    Inspect conf/config.yaml for admin_key values. The default key is 'edd1c9f034335f136f97ad3d9b'
    Affected if The admin_key or producer_key matches the default value 'edd1c9f034335f136f97ad3d9b'
  5. Check if IP restriction is configured on Admin API
    Review conf/config.yaml for enable_ip_checks or IP restriction plugin configuration on the Admin API route
    Affected if IP restriction is not configured or can be bypassed via batch-requests plugin

You are affected if Apache APISIX version is in the vulnerable range, the batch-requests plugin is enabled, and either the Admin API is network-accessible or the default API key is in use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.10.4 / 2.12.1 or later
Fixed in 2.10.42.12.1
Interim mitigation

Upgrade Apache APISIX to the patched version. If immediate patching is not possible, disable or restrict the batch-requests plugin and ensure Admin API is not exposed to untrusted networks.

Recommended fix High confidence

2.10.4 (for 2.10.x branch) or 2.12.1 (for 2.11.x/2.12.x branch)

  1. Upgrade Apache APISIX to version 2.10.4 or later if using the 2.10.x branch
  2. OR upgrade Apache APISIX to version 2.12.1 or later if using the 2.11.x or 2.12.x branch
  3. After upgrading, verify the batch-requests plugin configuration and ensure Admin API access controls are properly configured
  4. Consider changing the default Admin API key if not already done
Caveat Review plugin configurations and any custom batch-requests handling after upgrade as behavior may have changed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Apisix Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-24112 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-24112 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data