dbcve.org
StreamparkApplication · Apache

CVE-2024-29120

MEDIUM · 5.9 CVSS v3.1 Published 2024-07-17
Fix available
A fix is available. Upgrade to 2.1.4 or later.
See remediation →
64/100
Remediation priority · Elevated
No privileges 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
In Streampark (version < 2.1.4), when a user logged in successfully, the Backend service would return "Authorization" as the front-end authentication credential. User can use this credential to request other users' information, including the administrator's username, password, salt value, etc.  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

In Streampark before version 2.1.4, the backend returns an 'Authorization' credential upon successful login that can be reused to access other users' data through API endpoints, exposing sensitive information including administrator usernames, passwords, and salt values. This is a vertical privilege escalation/IDOR vulnerability allowing authenticated users to view other users' credentials.

MitigationUpgrade Streampark to version 2.1.4 or later to obtain the patched version with proper authorization controls.

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.0.0, < 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
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 the installed Streampark version
    Locate the Streampark installation and check the version file or web UI footer. The version is typically visible in the application or can be found in configuration files within the Streampark deployment directory.
    Affected if The version is >= 2.0.0 and < 2.1.4
  2. Verify the login API returns an Authorization token
    Use a tool like curl to send a POST request to the login endpoint (typically /api/user/login or similar) with valid user credentials. Inspect the response for an 'Authorization' field or token being returned.
    Affected if The login response includes an Authorization token that can be used for subsequent API requests
  3. Test for IDOR vulnerability in user data endpoints
    After obtaining an Authorization token for a regular user, make API requests to endpoints that retrieve user information (such as /api/user/list or /api/user/info) and observe if the API returns data for other users including sensitive fields like passwords and salts.
    Affected if An authenticated user can access credentials, password hashes, or salt values belonging to other users through the API

Your environment is affected if the installed Streampark version is between 2.0.0 and 2.1.3 inclusive AND the login returns an Authorization token that permits access to other users' credential data through API endpoints.

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 Streampark to version 2.1.4 or later to obtain the patched version with proper authorization controls.

Recommended fix High confidence

2.1.4

  1. 1. Backup your current Streampark configuration, database, and any custom configurations.
  2. 2. Consult the official Streampark upgrade documentation for version 2.1.4 to understand migration requirements.
  3. 3. Stop the Streampark services.
  4. 4. Upgrade Streampark to version 2.1.4 following the official installation/upgrade guide.
  5. 5. Verify the upgrade by checking that the login response no longer returns sensitive authorization credentials in plain text.
  6. 6. Confirm that user authentication works correctly and that the vulnerability is remediated by attempting to access other users' information with an authorization token (the request should be denied).
  7. 7. Restart all Streampark services and monitor for any issues.
Caveat Review release notes for 2.1.4 to check for any breaking changes or migration steps required from versions 2.0.0-2.1.3

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

Fix this in Streampark Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-29120 — 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-29120 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