Hyland OnBase up to 18.0.0.32/19.8.9.1000 ASP.NET BinaryFormatter.Deserialize SOAP Message deserialization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Hyland OnBase up to 18.0.0.32/19.8.9.1000. This affects the function BinaryFormatter.Deserialize of the component ASP.NET. This manipulation as part of SOAP Message causes deserialization.
This vulnerability is registered as CVE-2020-25258. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in Hyland OnBase up to 18.0.0.32/19.8.9.1000. It has been declared as critical. Affected by this vulnerability is the function BinaryFormatter.Deserialize of the component ASP.NET. The manipulation as part of a SOAP Message leads to a deserialization vulnerability. The CWE definition for the vulnerability is CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
An issue was discovered in Hyland OnBase through 18.0.0.32 and 19.x through 19.8.9.1000. It uses ASP.NET BinaryFormatter.Deserialize in a manner that allows attackers to transmit and execute bytecode in SOAP messages.
The weakness was published 09/11/2020. This vulnerability is known as CVE-2020-25258 since 09/11/2020. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. 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.
Similar entries are available at VDB-161127, VDB-161126, VDB-161124 and VDB-161123. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
- 18.0.0.0
- 18.0.0.1
- 18.0.0.2
- 18.0.0.3
- 18.0.0.4
- 18.0.0.5
- 18.0.0.6
- 18.0.0.7
- 18.0.0.8
- 18.0.0.9
- 18.0.0.10
- 18.0.0.11
- 18.0.0.12
- 18.0.0.13
- 18.0.0.14
- 18.0.0.15
- 18.0.0.16
- 18.0.0.17
- 18.0.0.18
- 18.0.0.19
- 18.0.0.20
- 18.0.0.21
- 18.0.0.22
- 18.0.0.23
- 18.0.0.24
- 18.0.0.25
- 18.0.0.26
- 18.0.0.27
- 18.0.0.28
- 18.0.0.29
- 18.0.0.30
- 18.0.0.31
- 18.0.0.32
- 19.8.0
- 19.8.1
- 19.8.2
- 19.8.3
- 19.8.4
- 19.8.5
- 19.8.6
- 19.8.7
- 19.8.8
- 19.8.9.1000
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: DeserializationCWE: CWE-502 / CWE-20
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
09/11/2020 🔍09/11/2020 🔍
09/11/2020 🔍
09/11/2020 🔍
Sources
Status: Not definedCVE: CVE-2020-25258 (🔍)
GCVE (CVE): GCVE-0-2020-25258
GCVE (VulDB): GCVE-100-161125
See also: 🔍
Entry
Created: 09/11/2020 11:04Updated: 09/11/2020 11:09
Changes: 09/11/2020 11:04 (38), 09/11/2020 11:09 (17)
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.