LogicalDoc CommunityEdition up to 7.5.3 XML xml external entity reference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.0 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical was found in LogicalDoc CommunityEdition up to 7.5.3. Affected is an unknown function of the component XML Handler. Such manipulation leads to xml external entity reference. This vulnerability is documented as CVE-2017-1000021. The attack can be executed remotely. There is not any exploit available.
Details
A vulnerability was found in LogicalDoc CommunityEdition up to 7.5.3 and classified as critical. Affected by this issue is an unknown function of the component XML Handler. 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. CVE summarizes:
LogicalDoc CommunityEdition 7.5.3 and prior is vulnerable to XXE when indexing XML documents.
The bug was discovered 07/10/2017. The weakness was released 07/17/2017 (Website). The advisory is available at blog.logicaldoc.com. This vulnerability is handled as CVE-2017-1000021 since 07/10/2017. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. The technical details are unknown and an exploit is not available.
The vulnerability was handled as a non-public zero-day exploit for at least 7 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.
Entries connected to this vulnerability are available at VDB-103587 and VDB-103588. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 8.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.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
07/10/2017 🔍07/10/2017 🔍
07/17/2017 🔍
07/17/2017 🔍
07/17/2017 🔍
10/26/2019 🔍
Sources
Advisory: blog.logicaldoc.comStatus: Not defined
CVE: CVE-2017-1000021 (🔍)
GCVE (CVE): GCVE-0-2017-1000021
GCVE (VulDB): GCVE-100-103586
See also: 🔍
Entry
Created: 07/17/2017 20:20Updated: 10/26/2019 09:52
Changes: 07/17/2017 20:20 (57), 10/26/2019 09:52 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.