Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-46647: CWE-302 Authentication Bypass by Assumed-Immutable Data in Apache Software Foundation Apache APISIX

0
Medium
VulnerabilityCVE-2025-46647cvecve-2025-46647cwe-302
Published: Wed Jul 02 2025 (07/02/2025, 11:08:47 UTC)
Source: CVE Database V5
Vendor/Project: Apache Software Foundation
Product: Apache APISIX

Description

A vulnerability of plugin openid-connect in Apache APISIX. This vulnerability will only have an impact if all of the following conditions are met: 1. Use the openid-connect plugin with introspection mode 2. The auth service connected to openid-connect provides services to multiple issuers 3. Multiple issuers share the same private key and relies only on the issuer being different If affected by this vulnerability, it would allow an attacker with a valid account on one of the issuers to log into the other issuer. This issue affects Apache APISIX: until 3.12.0. Users are recommended to upgrade to version 3.12.0 or higher.

AI-Powered Analysis

AILast updated: 11/04/2025, 21:50:34 UTC

Technical Analysis

CVE-2025-46647 is an authentication bypass vulnerability categorized under CWE-302, found in the openid-connect plugin of Apache APISIX, a popular open-source API gateway. The vulnerability specifically affects deployments using the openid-connect plugin in introspection mode where the authentication service supports multiple issuers that share the same private key and rely solely on the issuer claim to differentiate authentication contexts. Under these conditions, the plugin incorrectly assumes the immutability and uniqueness of issuer data, allowing an attacker who has a valid account on one issuer to authenticate as a user on another issuer without proper authorization. This flaw arises because the plugin does not sufficiently validate the cryptographic binding between tokens and issuers when the same private key is reused, leading to an authentication bypass. The vulnerability affects all versions of Apache APISIX prior to 3.12.0, where the issue has been fixed. Exploitation requires network access and low privileges but no user interaction. The CVSS v3.1 base score is 5.3 (medium), reflecting the moderate impact on confidentiality with no impact on integrity or availability, and a high attack complexity due to the specific configuration prerequisites. No known exploits are currently reported in the wild.

Potential Impact

For European organizations, this vulnerability could lead to unauthorized access across different issuer domains within the same authentication infrastructure, potentially compromising sensitive data and services protected by Apache APISIX. Organizations using multi-issuer OpenID Connect setups with shared private keys are at risk of cross-issuer impersonation, which could undermine trust boundaries and lead to data leakage or unauthorized service access. This is particularly critical for sectors with strict data protection regulations such as finance, healthcare, and government, where identity and access management integrity is paramount. The impact is limited to confidentiality breaches without direct integrity or availability effects, but the breach of authentication boundaries can facilitate further attacks or data exfiltration. The medium severity score indicates a moderate risk that should be addressed promptly to prevent lateral movement or privilege escalation within federated identity environments.

Mitigation Recommendations

European organizations should immediately assess their Apache APISIX deployments to determine if the openid-connect plugin is used in introspection mode with multiple issuers sharing the same private key. The primary mitigation is to upgrade Apache APISIX to version 3.12.0 or later, where this vulnerability has been patched. Additionally, organizations should avoid sharing private keys across multiple issuers and ensure that each issuer uses distinct cryptographic keys to maintain strong issuer binding. Implement strict validation of tokens to verify both issuer and cryptographic signatures independently. Conduct thorough audits of identity provider configurations to detect any insecure key sharing practices. Employ network segmentation and access controls to limit exposure of the authentication service. Monitoring and logging authentication attempts across issuers can help detect anomalous cross-issuer access patterns. Finally, consider deploying additional multi-factor authentication layers to reduce the risk of unauthorized access even if token validation is bypassed.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
apache
Date Reserved
2025-04-26T15:02:23.758Z
Cvss Version
null
State
PUBLISHED

Threat ID: 686516ee6f40f0eb72926ecc

Added to database: 7/2/2025, 11:24:30 AM

Last enriched: 11/4/2025, 9:50:34 PM

Last updated: 12/3/2025, 4:15:28 AM

Views: 225

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats