🛡️ CVE-2024-34457 — streampark

🟡 CVSS 6.5 — Medium ✅ No Known Exploit CWE-639 NVD
6.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

On versions before 2.1.4, after a regular user successfully logs in, they can manually make a request using the authorization token to view everyone's user flink information, including executeSQL and config.

Mitigation:

all users should upgrade to 2.1.4

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity none, availability none.

Weakness class

CVE-2024-34457 is classified as CWE-639: Authorization Bypass Through User-Controlled Key. An object is selected by an identifier from the request without checking the caller owns it.

Affected software

CVE-2024-34457 is recorded against 1 package.

  • streampark (fixed in 2.1.4)

Timeline and source

Published on 22 July 2024 and last revised on 17 June 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

lists.apache.org
www.openwall.com
www.openwall.com
lists.apache.org

Details

Severity MEDIUM
CVSS Score 6.5
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CWE CWE-639
Public Exploit ✅ No
Source NVD
Published 2024-07-22
Updated 2026-08-11
Modified 2026-06-17
Fix URL N/A

Affected Packages

Software From version Fixed in
streampark — 2.1.4

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in streampark

CVE-2024-34457 is rated CVSS 6.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.