weixin-java-tools 3.2.0 BaseWxPayResult.java getXmlDoc xml external entity reference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in weixin-java-tools 3.2.0. It has been rated as critical. Affected by this issue is the function getXmlDoc of the file BaseWxPayResult.java. The manipulation leads to xml external entity reference.
This vulnerability is documented as CVE-2018-20318. The attack can be initiated remotely. There is not any exploit available.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Details
A vulnerability, which was classified as critical, has been found in weixin-java-tools 3.2.0 (Programming Language Software). This issue affects the function getXmlDoc of the file BaseWxPayResult.java. The manipulation with an unknown input leads to a xml external entity reference vulnerability. Using CWE to declare the problem leads to CWE-611. The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
An issue was discovered in weixin-java-tools v3.2.0. There is an XXE vulnerability in the getXmlDoc method of the BaseWxPayResult.java file.
The bug was discovered 12/20/2018. The weakness was released 12/21/2018 (Website). The advisory is shared at github.com. The identification of this vulnerability is CVE-2018-20318 since 12/20/2018. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: Xml external entity referenceCWE: CWE-611 / CWE-610
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/20/2018 🔍12/20/2018 🔍
12/20/2018 🔍
12/21/2018 🔍
12/21/2018 🔍
06/20/2023 🔍
Sources
Advisory: 889Status: Not defined
CVE: CVE-2018-20318 (🔍)
GCVE (CVE): GCVE-0-2018-20318
GCVE (VulDB): GCVE-100-128261
Entry
Created: 12/21/2018 01:05 PMUpdated: 06/20/2023 02:22 PM
Changes: 12/21/2018 01:05 PM (56), 04/23/2020 09:28 AM (1), 06/20/2023 02:22 PM (3)
Complete: 🔍
Cache ID: 244:EDF:40
No comments yet. Languages: en.
Please log in to comment.