On versions before 2.1.4, session is not invalidated after logout. When the user logged in successfully, the Backend service returns "Authorization" as the front-end authentication credential. "Authorization" can still initiate requests and access data even after logout. Mitigation: all users should upgrade to 2.1.4
After successful login, the Apache Streampark backend returns an 'Authorization' token that serves as authentication credentials in communication with the frontend. The vulnerability lies in the fact that after user logout, the server does not invalidate the issued token (lack of proper session lifecycle management, CWE-613). This means that anyone who has intercepted or copied the token can still send authenticated requests to the backend and access protected resources, even though the account owner has formally logged out.
An attacker with a valid token can gain unauthorized access to sensitive data (high confidentiality) and potentially cause resource unavailability (high availability), without requiring any privileges or user interaction.
Apache Streampark should be updated immediately to version 2.1.4 or later, in which the session is properly invalidated after logout. According to the vendor's recommendation, all users should perform this update.
Apache Streampark in all versions before 2.1.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:HApache Streampark
APPApache1.0.0 – 2.1.4 (excl.)
Related vulnerabilities
Apache StreamPark: zakodowany na stałe klucz szyfrowania (CVE-2025-54947)
Apache StreamPark — nieautoryzowana modyfikacja kont użytkowników
Apache Streampark — nieograniczony upload plików JAR umożliwia RCE
Weak Encryption Algorithm in StreamPark, The use of an AES cipher in ECB mode and a weak random number generat...
Incorrect Execution-Assigned Permissions vulnerability in Apache StreamPark. This issue affects Apache Stream...