CVE-2024-8995: CWE-613: Insufficient Session Expiration in WSO2 WSO2 API Manager
WSO2 API Manager versions 3.1.0 through 4.6.0 have a vulnerability where unused authorization codes issued to deleted users are not properly invalidated. This allows these codes to persist and potentially be reused by attackers who have the authorization code and client credentials, enabling unauthorized access to resources within the scope of the original authorization.
AI Analysis
Technical Summary
CVE-2024-8995 is an insufficient session expiration vulnerability (CWE-613) in WSO2 API Manager. Authorization codes issued to users who have been deleted are not invalidated or removed, allowing these codes to remain valid. An attacker possessing both the authorization code and the associated client credentials (client ID and secret) can reuse these codes to obtain access tokens on behalf of deleted users. This can lead to unauthorized access to sensitive resources and services, depending on the scopes authorized by the compromised code. The vulnerability affects multiple versions from 3.1.0 through 4.6.0. No official patch or remediation level has been published yet, and there are no known exploits in the wild.
Potential Impact
The vulnerability allows attackers with access to unused authorization codes and client credentials to obtain access tokens for deleted users, potentially granting unauthorized access to sensitive resources within the scope of the original authorization. The CVSS score of 4.9 (medium severity) reflects limited attack complexity and low privileges required, but with potential confidentiality and integrity impacts. There is no indication of availability impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, organizations should consider restricting access to authorization codes and client credentials, and monitor for unusual token issuance patterns related to deleted users. Follow vendor updates closely for an official fix or mitigation instructions.
CVE-2024-8995: CWE-613: Insufficient Session Expiration in WSO2 WSO2 API Manager
Description
WSO2 API Manager versions 3.1.0 through 4.6.0 have a vulnerability where unused authorization codes issued to deleted users are not properly invalidated. This allows these codes to persist and potentially be reused by attackers who have the authorization code and client credentials, enabling unauthorized access to resources within the scope of the original authorization.
CVSS v3.1
Score 4.9medium
Affected software
WSO2
WSO2 API Manager
WSO2
WSO2 Traffic Manager
WSO2
WSO2 API Control Plane
WSO2
WSO2 Universal Gateway
WSO2
WSO2 Open Banking AM
WSO2
WSO2 Identity Server
WSO2
WSO2 Open Banking IAM
WSO2
WSO2 Identity Server as Key Manager
WSO2
WSO2 Carbon OAuth
pkg:maven/org.wso2/carbon-apimgtRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2024-8995 is an insufficient session expiration vulnerability (CWE-613) in WSO2 API Manager. Authorization codes issued to users who have been deleted are not invalidated or removed, allowing these codes to remain valid. An attacker possessing both the authorization code and the associated client credentials (client ID and secret) can reuse these codes to obtain access tokens on behalf of deleted users. This can lead to unauthorized access to sensitive resources and services, depending on the scopes authorized by the compromised code. The vulnerability affects multiple versions from 3.1.0 through 4.6.0. No official patch or remediation level has been published yet, and there are no known exploits in the wild.
Potential Impact
The vulnerability allows attackers with access to unused authorization codes and client credentials to obtain access tokens for deleted users, potentially granting unauthorized access to sensitive resources within the scope of the original authorization. The CVSS score of 4.9 (medium severity) reflects limited attack complexity and low privileges required, but with potential confidentiality and integrity impacts. There is no indication of availability impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, organizations should consider restricting access to authorization codes and client credentials, and monitor for unusual token issuance patterns related to deleted users. Follow vendor updates closely for an official fix or mitigation instructions.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- WSO2
- Date Reserved
- 2024-09-19T08:21:20.017Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a7441c2bf8831d53967eba9
Added to database: 08/06/2026, 08:11:46 UTC
Last enriched: 08/13/2026, 17:32:52 UTC
Last updated: 09/21/2026, 22:01:27 UTC
Views: 60
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.