Back to the CVE list
CVE-2024-9517

Improper Token Renewal in Refresh Token Grant in Multiple WSO2 Products Allows Unauthorized Access to Blocked Accounts

CVSS score

4.9

EPSS probability

—

Risk score

0.5

Published

1 h ago

Patch status has not yet been verified

Resmî kaynaklarda yeterli kanıt bulunamadı. Bu sonuç “yama yok” anlamına gelmez.

Impact on My Inventory

Only the personal products you have added to your account are assessed; an organisation's inventory does not appear here.

Checking session…

Vulnerability description

DayBreach AI Explanation

Verified against sources

CVE-2024-9517: Improper Token Renewal Vulnerability in WSO2 Products

Sources read

1

Source agreement

Tam uyum

Evidence confidence

%55

Short explanation

Multiple WSO2 products contain a vulnerability caused by the refresh token grant type failing to re-validate account status. This weakness allows attackers to obtain valid access tokens for blocked accounts, bypassing account lockout mechanisms.

Why does it matter?

It enables unauthorized access to blocked user accounts, potentially allowing attackers to perform actions on behalf of blocked users, escalate privileges, or exfiltrate data.

What should be done?

  • Follow the vendor security advisory
  • Apply available updates for affected products
Chain of evidence and sources2 verified claims

WSO2 ürünlerindeki yenileme token grant türü, yeni erişim token'ları düzenlemeden önce hesap durumunu yeniden doğrulamamaktadır.

Bu zafiyet, kullanıcı deposu tarafından engellenen hesaplar için dahi geçerli erişim token'ları alınmasına ve hesap kilitleme mekanizmalarının atlanmasına neden olur.

Show the technical text from the sources

The refresh token grant type in WSO2 products fails to re-validate account status before issuing new access tokens. This weakness allows an attacker to obtain valid access tokens for user accounts even after they have been blocked by the user store, bypassing account lockout mechanisms. This vulnerability can lead to unauthorized access to user accounts and their associated resources. Attackers can leverage this to perform actions on behalf of blocked users, potentially leading to privilege escalation or data exfiltration depending on the permissions of the compromised account.

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

CWE: CWE-613

This explanation was compiled automatically from the source records. Scores, active exploitation, patch and exploit status come straight from the sources.

IMPACT: Affected Products and Software

Affected Products

The following products are affected by CVE-2024-9517 vulnerability. Where our threat engine knows the exact affected versions, they are listed below.

IDVENDORPRODUCTACTION
1wso2WSO2 API Manager View
2wso2WSO2 Universal Gateway View
3wso2WSO2 Traffic Manager View
4wso2WSO2 API Control Plane View
5wso2WSO2 Identity Server as Key Manager View
6wso2WSO2 Identity Server View
7wso2WSO2 Open Banking AM View
8wso2WSO2 Open Banking IAM View
9wso2WSO2 Carbon OAuth View
Total affected vendors: 1|Products: 9

RED HAT CSAF/VEX: Product Impact Check

Red Hat has not yet published a CSAF/VEX impact record for this CVE. This does not mean “not affected”.

SCORING: CVSS from Multiple Sources

CVSS Scores

The Common Vulnerability Scoring System is a standardised framework for assessing the severity of vulnerabilities in software and systems. We collect and display CVSS scores from several sources for each CVE.

SCOREVERSIONSEVERITYVECTORSOURCE
4.9CVSS V3_1MEDIUMCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:NCVE CNA

Patch and Remediation Guide

Solution & Remediation Advisory

Patch status unknown

İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.

Confirm the affected product and version against the source evidence above.
Restrict access to internet-facing services and apply network segmentation.
Until a patch is confirmed, follow the vendor advisory; do not read an unknown status as “no patch”.
Monitor server logs and network endpoints for signs of anomalous execution.

Public exploit and active exploitation status

Verified exploit intelligence

No verified public PoC, exploit repository or Metasploit module has been found for this CVE yet.

Weakness Classification and Attack Patterns (CWE & CAPEC)

CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorises the common flaws or weaknesses that can lead to vulnerabilities. CVE-2024-9517 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2024-9517 weaknesses.

Attack Vector and Accessibility

ExposureAğ üzerinden
PermissionsLow
UserGerekmiyor

Official Sources and Advisories

CVSS Vector Radar Chart

4.9 / 10
Attack VectorNetworkComplexityHighPrivilegesLowUser Interact.NoneConfidentialityHighIntegrityNoneAvailabilityNone

Vulnerability Scoring Details

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N
Attack VectorNetwork
Attack ComplexityHigh
Privileges RequiredLow privileges
User InteractionNone required
Confidentiality (Gizlilik)High
Integrity (Bütünlük)None
Availability (Erişilebilirlik)None

Yama durumu bilinmiyor

İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.

Follow the vendor

W
wso2 logo
wso2

Weakness Type (CWE & CAPEC)

Similar Vulnerabilities

Get this vulnerability through the API

Affected products, version ranges, exploitation status and patch information in a single request, with a free key.

curl -H "x-api-key: $DAYBREACH_API_KEY" \
  "https://api.daybreach.dev/api/v1/intel/cves/CVE-2024-9517"