JEECMS getRemoteImage.jspx upfile server-side request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in JEECMS. It has been classified as critical. The affected element is an unknown function of the file ueditor/getRemoteImage.jspx. This manipulation of the argument upfile as part of Parameter causes server-side request forgery. This vulnerability is tracked as CVE-2018-20528. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability has been found in JEECMS (unknown version) and classified as critical. Affected by this vulnerability is an unknown code block of the file ueditor/getRemoteImage.jspx. The manipulation of the argument upfile as part of a Parameter leads to a server-side request forgery vulnerability. The CWE definition for the vulnerability is CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
JEECMS 9 has SSRF via the ueditor/getRemoteImage.jspx upfile parameter.
The bug was discovered 12/27/2018. The weakness was disclosed 12/28/2018 (Website). The advisory is shared at hacker.feiyulive.com. This vulnerability is known as CVE-2018-20528 since 12/27/2018. The exploitation appears to be easy. The attack can be launched remotely. The requirement for exploitation is a single authentication. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.4
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Server-side request forgeryCWE: CWE-918
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/27/2018 🔍12/27/2018 🔍
12/28/2018 🔍
12/28/2018 🔍
12/29/2018 🔍
06/22/2023 🔍
Sources
Advisory: hacker.feiyulive.comStatus: Not defined
CVE: CVE-2018-20528 (🔍)
GCVE (CVE): GCVE-0-2018-20528
GCVE (VulDB): GCVE-100-128497
X-Force: 154855
Entry
Created: 12/29/2018 17:23Updated: 06/22/2023 10:57
Changes: 12/29/2018 17:23 (56), 04/24/2020 20:29 (1), 06/22/2023 10:57 (3)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.