For Eclipse Jetty versions <= 9.4.40, <= 10.0.2, <= 11.0.2, if an exception is thrown from the SessionListener#sessionDestroyed() method, then the session ID is not invalidated in the session ID manager. On deployments with clustered sessions and multiple contexts this can result in a session not being invalidated. This can result in an application used on a shared computer being left logged in.
References
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Configuration 3 (hide)
|
Configuration 4 (hide)
|
History
07 Nov 2023, 03:35
Type | Values Removed | Values Added |
---|---|---|
References |
|
|
Information
Published : 2021-06-22 15:15
Updated : 2024-02-28 18:28
NVD link : CVE-2021-34428
Mitre link : CVE-2021-34428
CVE.ORG link : CVE-2021-34428
JSON object : View
Products Affected
oracle
- communications_session_report_manager
- communications_element_manager
- siebel_core_-_automation
- communications_services_gatekeeper
- autovue_for_agile_product_lifecycle_management
- communications_session_route_manager
- rest_data_services
debian
- debian_linux
netapp
- snap_creator_framework
- element_plug-in_for_vcenter_server
- e-series_santricity_os_controller
- snapmanager
- active_iq_unified_manager
- santricity_cloud_connector
- e-series_santricity_web_services
eclipse
- jetty
CWE
CWE-613
Insufficient Session Expiration