dbcve.org
StreamparkApplication · Apache

CVE-2024-29178

HIGH · 8.8 CVSS v3.1 Published 2024-07-18
Fix available
A fix is available. Upgrade to 2.1.4 or later.
See remediation →
94/100
Remediation priority · Urgent
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, a user could log in and perform a template injection attack resulting in Remote Code Execution on the server, The attacker must successfully log into the system to launch an attack, so this is a moderate-impact vulnerability. 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 · moderate confidence

An authenticated template injection vulnerability in versions before 2.1.4 allows logged-in users to inject malicious template code that gets executed server-side, leading to remote code execution. Attackers exploit the template rendering engine by submitting specially crafted input through user-accessible functions.

MitigationUpgrade to version 2.1.4 immediately. Since this is an authenticated attack vector, ensure compromised credentials are rotated as part of remediation.

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
High
Availability
High

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

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 if Apache Streampark is deployed
    Check for running Java processes or look for Streampark installation directories, typically under /opt/streampark, /usr/local/streampark, or the application's deployment path
    Affected if Apache Streampark is found running or installed on the system
  2. Determine the installed Streampark version
    Check the version file or pom.xml in the Streampark installation directory, or query the application's web interface version endpoint if available
    Affected if The version is lower than 2.1.4 (e.g., 2.1.3, 2.1.2, 2.1.0, or any pre-2.1.4 release)
  3. Verify user authentication is enabled
    Examine the application configuration files (application.yml or application.properties) for authentication settings such as spring.security.user.name/password or similar security configurations
    Affected if Authentication is disabled or uses default credentials, allowing unauthenticated access to user-facing functions
  4. Check if user registration or account creation is allowed
    Review the security configuration to determine if self-registration is enabled or if low-privilege user accounts can be created through the web interface
    Affected if Users can register new accounts or obtain valid session credentials through the application

You are affected if Apache Streampark version is below 2.1.4 AND the application allows user authentication or account creation, enabling a logged-in user to access template rendering features.

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 immediately. Since this is an authenticated attack vector, ensure compromised credentials are rotated as part of remediation.

Recommended fix High confidence

Streampark 2.1.4

  1. 1. Back up your current Streampark installation, configuration files, and databases before upgrading
  2. 2. Download Streampark version 2.1.4 from the official Apache repository or release page
  3. 3. Stop the currently running Streampark service
  4. 4. Install or deploy version 2.1.4 following the standard installation procedure
  5. 5. Verify the upgrade was successful by checking the version number in the application
  6. 6. Restart the Streampark service
  7. 7. Log in and verify that normal functionality works correctly
  8. 8. Test that the template injection vulnerability is no longer present
Caveat Review release notes for any configuration or feature 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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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