e-Contract dssp up to 1.3.1 SignResponseVerifier.java checkSignResponse xml external entity reference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in e-Contract dssp up to 1.3.1 and classified as problematic. This affects the function checkSignResponse of the file dssp-client/src/main/java/be/e_contract/dssp/client/SignResponseVerifier.java. This manipulation causes xml external entity reference.
The identification of this vulnerability is CVE-2016-15011. There is no exploit available.
The affected component should be upgraded.
Details
A vulnerability classified as problematic was found in e-Contract dssp up to 1.3.1. Affected by this vulnerability is the function checkSignResponse of the file dssp-client/src/main/java/be/e_contract/dssp/client/SignResponseVerifier.java. The manipulation with an unknown input leads to a xml external entity reference vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was shared 01/06/2023 as ec4238349691ec66dd30b416ec6eaab02d722302. The advisory is shared at github.com. This vulnerability is known as CVE-2016-15011. Technical details are known, but no exploit is available.
Upgrading to version 1.3.2 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch ec4238349691ec66dd30b416ec6eaab02d722302 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version. The advisory contains the following remark:
5342: fix XML external entity injection
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
- Product: https://github.com/e-Contract/dssp/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.9VulDB Meta Temp Score: 6.9
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 5.5
CNA Vector (VulDB): 🔍
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: dssp 1.3.2
Patch: ec4238349691ec66dd30b416ec6eaab02d722302
Timeline
01/06/2023 🔍01/06/2023 🔍
01/06/2023 🔍
01/29/2023 🔍
Sources
Product: github.comAdvisory: ec4238349691ec66dd30b416ec6eaab02d722302
Status: Confirmed
CVE: CVE-2016-15011 (🔍)
GCVE (CVE): GCVE-0-2016-15011
GCVE (VulDB): GCVE-100-217549
Entry
Created: 01/06/2023 10:51Updated: 01/29/2023 09:57
Changes: 01/06/2023 10:51 (45), 01/29/2023 09:52 (2), 01/29/2023 09:57 (28)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.