dbcve.org
ApisixApplication · Apache

CVE-2022-29266

HIGH · 7.5 CVSS v3.1 Published 2022-04-20
Fix available
A fix is available. Upgrade to 2.13.1 or later.
See remediation →
84/100
Remediation priority · High
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
In APache APISIX before 3.13.1, the jwt-auth plugin has a security issue that leaks the user's secret key because the error message returned from the dependency lua-resty-jwt contains sensitive information.

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

The jwt-auth plugin in APISIX versions before 3.13.1 has an information disclosure vulnerability where error messages from the lua-resty-jwt dependency are returned directly to users without sanitization. These error messages can contain the configured JWT secret key, allowing attackers to obtain the secret through crafted requests that trigger authentication errors.

MitigationUpgrade APISIX to version 3.13.1 or later, which includes sanitized error handling that prevents secret key exposure. Until upgraded, avoid exposing detailed error responses from the jwt-auth plugin publicly.

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.13.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
None
Availability
None

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

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. Identify installed APISIX version
    Run 'apisix version' or check the version in your deployment package, then compare it to the affected range (< 2.13.1)
    Affected if APISIX version is earlier than 2.13.1
  2. Verify jwt-auth plugin is enabled
    Check your apisix.yml configuration file for 'jwt-auth' in the plugins list, or query the APISIX admin API endpoint /apisix/admin/plugins
    Affected if The jwt-auth plugin is listed as enabled in your configuration
  3. Confirm public access to jwt-auth protected routes
    Review your route definitions that use the jwt-auth plugin and determine if they are exposed to unauthenticated network access (check consumer credentials and route definitions in apisix.yml or via /apisix/admin/routes)
    Affected if Publicly accessible routes exist that rely on jwt-auth for authentication
  4. Test for secret exposure in error responses
    Send a crafted request to a jwt-auth protected route with an invalid or malformed JWT token, then inspect the error response for any appearance of the configured secret key
    Affected if The error response contains all or part of your JWT secret key

You are affected if running APISIX version below 2.13.1 with the jwt-auth plugin enabled and publicly accessible, where authentication error responses expose your JWT secret key.

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.13.1 or later
Fixed in 2.13.1
Interim mitigation

Upgrade APISIX to version 3.13.1 or later, which includes sanitized error handling that prevents secret key exposure. Until upgraded, avoid exposing detailed error responses from the jwt-auth plugin publicly.

Recommended fix High confidence

Apache APISIX 3.13.1 (or latest stable release)

  1. 1. Identify all Apache APISIX instances running version < 3.13.1 (or < 2.13.1 depending on your version scheme)
  2. 2. Ensure you have a backup of your current configuration and data
  3. 3. Review the jwt-auth plugin configuration to identify any secrets that may have been exposed through error logs
  4. 4. Rotate any JWT secrets that may have been potentially leaked
  5. 5. Upgrade Apache APISIX to version 3.13.1 or later which contains the fix for the jwt-auth plugin information disclosure (CVE-2022-29266)
  6. 6. After upgrade, verify the jwt-auth plugin is functioning correctly and error messages no longer contain sensitive information
  7. 7. Review access logs for any evidence of the vulnerability being exploited prior to the upgrade
Caveat Review release notes for any breaking changes between your current version and 3.13.1; particularly note any configuration schema changes in the jwt-auth plugin

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

Fix this in Apisix Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-29266 — 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-29266 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