Hyland OnBase up to 18.0.0.32/19.8.9.1000 Client Application Log privileges management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Hyland OnBase up to 18.0.0.32/19.8.9.1000. It has been classified as critical. Affected by this vulnerability is an unknown functionality of the component Client Application Handler. The manipulation leads to privileges management (Log). This vulnerability is uniquely identified as CVE-2020-25250. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in Hyland OnBase up to 18.0.0.32/19.8.9.1000. It has been rated as critical. This issue affects an unknown code block of the component Client Application Handler. The manipulation with an unknown input leads to a privileges management vulnerability (Log). Using CWE to declare the problem leads to CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. Impacted is 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. Client applications can write arbitrary data to the server logs.
The weakness was disclosed 09/11/2020. The identification of this vulnerability is CVE-2020-25250 since 09/11/2020. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-161121, VDB-161120, VDB-161119 and VDB-161118 are pretty similar. 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: 7.4VulDB Meta Temp Score: 7.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.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
Name: LogClass: Privileges management / Log
CWE: CWE-269 / CWE-266
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-25250 (🔍)
GCVE (CVE): GCVE-0-2020-25250
GCVE (VulDB): GCVE-100-161117
See also: 🔍
Entry
Created: 09/11/2020 11:01Updated: 09/11/2020 11:06
Changes: 09/11/2020 11:01 (37), 09/11/2020 11:06 (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.