Horizon Alert
Summary of the vulnerability and why it matters
This advisory concerns a critical vulnerability in an older, unsupported version of Apache SeaTunnel Web. The issue allows authenticated users, even those whose accounts have been disabled, to obtain new login tokens and access protected APIs if they possess valid credentials for the disabled account. Given that this component is no longer maintained, the primary concern is to confirm if it is in use within the organization and identify any potential exposure.
- Disabled accounts can still log in.
- This is an unsupported, unpatched component.
- Confirm if this outdated software is in use.
Attack Path
How an attacker could exploit the issue
An attacker with valid credentials for a disabled account can log in to Apache SeaTunnel Web, obtain a new token, and access protected APIs. This occurs because the system does not check the account status during the login process. The vulnerability leads to unauthorized access and control over the affected system.
- Requires valid credentials for a disabled account.
- Login process bypasses account status check.
- Unauthorized access and token issuance.
Live Threat
Current exploitation, exposure, and threat context
When an account is disabled, a user with valid credentials could still authenticate and obtain a new login token. This is because the system does not check the account status during the authentication process. However, this vulnerability requires valid credentials for the disabled account and is not a bypass for authentication.
- System data and protected APIs could be accessed.
- Using valid credentials for a disabled account.
- Unauthorized access to sensitive information.
Operational Fix
Recommended remediation, mitigation, and detection steps
This vulnerability affects Apache SeaTunnel Web 1.0.2, which is no longer maintained. Because the product is unsupported, the primary action is to discontinue its use and migrate to an alternative solution. System owners and security teams should first identify all instances of this component and confirm their reachability and criticality before planning migration or implementing compensating controls if immediate discontinuation is not feasible.
- Discontinue use and migrate.
- Verify all affected instances.
- Plan for secure replacement.