CVE-2025-54947
CriticalCVSS 9.8Exploitation Probability (EPSS)
Low risk39th percentile - higher than 39% of all known CVEs
Summary
In Apache StreamPark versions 2.0.0 through 2.1.7, a security vulnerability involving a hard-coded encryption key exists. The system uses a fixed, immutable key for encryption instead of dynamically generating or securely configuring the key. Attackers may obtain this key through reverse engineering or code analysis, potentially decrypting sensitive data or forging encrypted information, leading to information disclosure or unauthorized system access.
Risk Assessment
Disclosure of the hardcoded key can lead to decryption of sensitive data or unauthorized access, posing a serious threat to system security.
Recommendation
It is recommended to upgrade to version 2.1.7, which fixes the issue, and implement dynamic key management.
Other vulnerabilities in Apache StreamPark
See all- CVE-2025-53960Medium
Apache StreamPark directly uses the user's password as the HMAC signing key (e.g., with the HS256 algorithm) when issuing JWT tokens. An attacker can exploit this to perform offline brute-force attacks on the user's password using a captured JWT, or to forge identity tokens if the password is known, leading to complete account takeover.
- CVE-2025-54981High
Weak Encryption Algorithm in Apache StreamPark: the use of an AES cipher in ECB mode and a weak random number generator for encrypting sensitive data, including JWT tokens, may have risked exposing sensitive authentication data. This affects versions from 2.0.0 before 2.1.7. Users are recommended to upgrade to version 2.1.7.
- CVE-2025-30001High
Apache StreamPark versions 2.1.4 through 2.1.5 have an incorrect execution-assigned permissions vulnerability. The issue is fixed in version 2.1.6.
Original NVD description (English source)
In Apache StreamPark versions 2.0.0 through 2.1.7, a security vulnerability involving a hard-coded encryption key exists. This vulnerability occurs because the system uses a fixed, immutable key for encryption instead of dynamically generating or securely configuring the key. Attackers may obtain this key through reverse engineering or code analysis, potentially decrypting sensitive data or forging encrypted information, leading to information disclosure or unauthorized system access. This issue affects Apache StreamPark: from 2.0.0 before 2.1.7. Users are recommended to upgrade to version 2.1.7, which fixes the issue.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS