Skip to content
Fencer Intel
critical 9.8

CVE-2022-45802 json

Apache StreamPark (incubating): Upload any file to any directory

published 3y ago modified 4mo ago also GHSA-6874-289g-f7h7 , EUVD-2023-1974

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.3%
EPSS 1.3% chance of exploitation in 30 days, percentile 70%
public exploits
0
none known

Summary

Streampark allows any users to upload a jar as application, but there is no mandatory verification of the uploaded file type, causing users to upload some high-risk files, and may upload them to any directory, Users of the affected versions should upgrade to Apache StreamPark 2.0.0 or later

Patch / fix

  • maven org.apache.streampark:streampark-common_2.12 2.0.0
  • maven org.apache.streampark:streampark-common_2.11 2.0.0
  • Apache Software Foundation Apache StreamPark (incubating) 2.0.0
  • apache streampark 2.0.0

Is CVE-2022-45802 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
2y ago

Exploit prediction

1.31% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CISA ADP 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.apache.streampark:streampark-common_2.12
<2.0.0
2.0.0
maven org.apache.streampark:streampark-common_2.11
<2.0.0
2.0.0

Affected products

  • Apache Software Foundation Apache StreamPark (incubating)
  • apache streampark

Classification

Weakness
  • CWE-434 Unrestricted Upload of File with Dangerous Type
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.