dbcve.org
StreamparkApplication · Apache

CVE-2024-34457

MEDIUM · 6.5 CVSS v3.1 Published 2024-07-22
Fix available
A fix is available. Upgrade to 2.1.4 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an Insecure Direct Object Reference (IDOR) or broken access control vulnerability in the Flink user information disclosure. After successful authentication, a regular user can use their authorization token to access other users' sensitive Flink information, including executeSQL and config data, indicating improper authorization checks on user-specific resources.

MitigationUpgrade to version 2.1.4 or later, which contains the fix for this authorization bypass that allowed regular users to view all users' Flink information.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
StreamparkApplication
Affected:< 2.1.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Streampark installation and version
    Locate the Streampark installation directory and check the version file, typically found in the installation root or via the web UI login page footer. Common paths include /opt/streampark or the application's about/info endpoint.
    Affected if The installed version is lower than 2.1.4, meaning the version is vulnerable to the authorization bypass.
  2. Confirm multi-user authentication is enabled
    Check the Streampark configuration files (typically in conf/ or config/ directory) for authentication settings. Verify that the authentication mechanism (such as LDAP, database-based, or other) is configured and enabled.
    Affected if Authentication is enabled and multiple user accounts exist, which creates the condition where the IDOR vulnerability can be exploited.
  3. Verify user-specific resource isolation configuration
    Inspect the application configuration for authorization or access control settings related to user-specific resources. Look for settings controlling access to user data endpoints, particularly those related to Flink executeSQL and config data.
    Affected if Authorization controls for user-specific resources are not properly configured or are missing, indicating the vulnerability may be present.
  4. Test cross-user resource access (requires test environment)
    Using two different regular user accounts, attempt to access resources belonging to the other user through the API or web interface. Specifically, try accessing executeSQL or config data endpoints using a valid token from one user but requesting another user's resources by modifying identifiers.
    Affected if A regular user can successfully access, view, or retrieve Flink information belonging to a different user, confirming the IDOR vulnerability is exploitable.

Your environment is affected if Apache Streampark version is below 2.1.4, multi-user authentication is enabled, and a regular user can access other users' Flink executeSQL or config data without proper authorization checks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.1.4 or later
Fixed in 2.1.4
Interim mitigation

Upgrade to version 2.1.4 or later, which contains the fix for this authorization bypass that allowed regular users to view all users' Flink information.

Recommended fix High confidence

Streampark 2.1.4

  1. 1. Back up your current Streampark installation and database
  2. 2. Download Streampark version 2.1.4 from the official Apache repository
  3. 3. Stop the running Streampark services
  4. 4. Upgrade the Streampark installation to version 2.1.4
  5. 5. Verify the upgrade by logging in as a regular user and confirming they can no longer access other users' flink information (executeSQL and config)
  6. 6. Restart all Streampark services
Caveat Review release notes for any configuration or API changes between your current version and 2.1.4

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Streampark Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-34457 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-34457 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data