Hyland OnBase up to 18.0.0.32/19.8.9.1000 PKI Certificate/Private Key hard-coded credentials
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.2 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Hyland OnBase up to 18.0.0.32/19.8.9.1000. The affected element is an unknown function of the component PKI Certificate/Private Key. The manipulation leads to hard-coded credentials. This vulnerability is listed as CVE-2020-25256. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability was found in Hyland OnBase up to 18.0.0.32/19.8.9.1000 and classified as critical. This issue affects an unknown code of the component PKI Certificate/Private Key. The manipulation with an unknown input leads to a hard-coded credentials vulnerability. Using CWE to declare the problem leads to CWE-798. The product contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. 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. PKI certificates have a private key that is the same across different customers' installations.
The weakness was presented 09/11/2020. The identification of this vulnerability is CVE-2020-25256 since 09/11/2020. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1110.001 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
See VDB-161127, VDB-161126, VDB-161125 and VDB-161124 for similar entries. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
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.2VulDB Meta Temp Score: 8.2
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.1
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: Hard-coded credentialsCWE: CWE-798 / CWE-259 / CWE-255
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-25256 (🔍)
GCVE (CVE): GCVE-0-2020-25256
GCVE (VulDB): GCVE-100-161123
See also: 🔍
Entry
Created: 09/11/2020 11:03Updated: 09/11/2020 11:08
Changes: 09/11/2020 11:03 (37), 09/11/2020 11:08 (17)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.