dbcve.org
StreamparkApplication · Apache

CVE-2024-48988

HIGH · 7.6 CVSS v3.1 Published 2025-08-22
Fix available
A fix is available. Upgrade to 2.1.6 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable No privileges

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
SQL Injection vulnerability in Apache StreamPark. This issue affects Apache StreamPark: from 2.1.4 before 2.1.6. Users are recommended to upgrade to version 2.1.6, which fixes the issue. This vulnerability is present only in the distribution package (SpringBoot platform) and does not involve Maven artifacts. It can only be exploited after a user has successfully logged into the platform (implying that the attacker would first need to compromise the login authentication). As a result, the associated risk is considered relatively low.

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

SQL Injection vulnerability in Apache StreamPark affecting versions 2.1.4 through 2.1.5 in the SpringBoot distribution package. Exploitation requires a valid authenticated user session, making the attack surface smaller than typical SQL injection vulnerabilities.

MitigationUpgrade Apache StreamPark to version 2.1.6 which contains the fix for this SQL injection vulnerability.

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, < 2.1.6

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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. Confirm Apache StreamPark is installed
    Look for StreamPark processes running (ps aux | grep streampark) or check for the StreamPark web interface on common ports (20000, 10000)
    Affected if StreamPark is running in the environment
  2. Identify the installed version
    Check the version file in the StreamPark installation directory, or view the startup logs which typically display the version on boot. Common paths: $STREAMPARK_HOME/version.properties or check the JAR/WAR file metadata.
    Affected if The version is 2.1.4 or 2.1.5 (or falls within >= 2.1.4 and < 2.1.6)
  3. Verify the SpringBoot distribution
    Check the deployment type - SpringBoot distributions typically contain a single JAR file (streampark-*.jar) and use an embedded server. Examine the file structure in the installation directory.
    Affected if The deployment is the SpringBoot distribution package
  4. Check if user authentication is configured
    Examine the configuration file (application.yml or application.properties) for authentication settings. Look for security-related configurations or user management settings.
    Affected if Authentication is enabled and user sessions can be obtained (exploitation requires valid authenticated user)
  5. Review application logs for suspicious SQL activity
    Search StreamPark logs for unusual SQL syntax, error messages containing SQL keywords, or unexpected database queries that may indicate exploitation attempts.
    Affected if Evidence of SQL injection attempts appears in the logs

If StreamPark version is 2.1.4 or 2.1.5 (or any version >= 2.1.4 and < 2.1.6) using the SpringBoot distribution, the environment is vulnerable to this SQL injection flaw when authentication is enabled.

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.6 or later
Fixed in 2.1.6
Interim mitigation

Upgrade Apache StreamPark to version 2.1.6 which contains the fix for this SQL injection vulnerability.

Recommended fix High confidence

2.1.6

  1. 1. Download Apache StreamPark version 2.1.6 from the official Apache download source (e.g., apache.streampark.com)
  2. 2. Review the official Apache StreamPark upgrade documentation for migration notes
  3. 3. Create a complete backup of the current StreamPark installation including database, configuration files, and any custom settings
  4. 4. Stop the currently running StreamPark service
  5. 5. Replace the existing StreamPark installation with the new 2.1.6 version, preserving configuration files or migrating them as documented
  6. 6. Start the StreamPark 2.1.6 service
  7. 7. Verify the application starts successfully and all functionalities work as expected
  8. 8. Confirm the SQL injection vulnerability is resolved by testing the previously vulnerable functionality
Caveat Refer to release notes for any configuration or feature changes between 2.1.4/2.1.5 and 2.1.6; no major breaking changes mentioned in provided description

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

Fix this in Streampark Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,340
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,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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