Apache StreamPark: Use hard-coded key vulnerability
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Apache Software Foundation | Apache StreamPark | unaffected |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Apache | Streampark | — |
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-prv5-c2px-j9q3 | Apache StreamPark has a hard-coded encryption key |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.496% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-798 | |
| CPEs | cpe:2.3:a:apache:streampark:*:*:*:*:*:*:*:* |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Apache
Apache streampark |
|
| Vendors & Products |
Apache
Apache streampark |
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Apache StreamPark: Use hard-coded key vulnerability | |
| Weaknesses | CWE-321 | |
| References |
|