제출 #962567: y_project RuoYi 4.8.3 Insufficient Session Expiration정보

제목y_project RuoYi 4.8.3 Insufficient Session Expiration
설명RuoYi 4.8.3 (commit 1a19343edc330b01d205c51f1cbcf02b557e7d14) has an insufficient session expiration issue. Disabling a user only updates sys_user.status to 1. New logins are rejected with "用户已封禁,请联系管理员", but changeStatus does not destroy the target user's live Shiro/OnlineSession objects. Later requests only check whether the OnlineSession is marked off_line and do not re-read sys_user.status. A holder of a pre-disable JSESSIONID can still call protected APIs that the account already had permission to use. In a local test, the old cookie succeeded on POST /system/config/add after disable and created a sys_config row with create_by=cachevictim. A fresh login with the same credentials was rejected. The disable API itself still requires system:user:edit. This is not an unauthenticated write and not a new-role grant. Impact is bounded by the disabled account's original permissions. This is distinct from CVE-2024-57436 (session ID leak), CVE-2025-4819 (force-logout authorization), CVE-2025-10384 (role cancelAll authorization), and CVE-2025-28405 (job changeStatus).
원천⚠️ https://github.com/Bob-wentao/security-report-for-ruoyi-csrf-get-delete/blob/main/security-report-ruoyi-4.8.3-insufficient-session-expiration.md
사용자
 bobtao666 (UID 100998)
제출2026. 09. 06. PM 07:45 (1 월 ago)
모더레이션2026. 10. 11. AM 11:36 (1 month later)
상태수락
VulDB 항목416580 [y_project RuoYi 까지 4.8.3 Disable API /system/config/add changeStatus 약한 인증]
포인트들20

Do you know our Splunk app?

Download it now for free!