Weak Password Hash in Core Privileged Access Manager (BoKS)
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Fortra | Core Privileged Access Manager (BoKS) | unaffected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Fortra | Boks | — |
Vendor Solution
Upgrade to BoKS Server Agent 9.0.0.4.
Vendor Workaround
Configure the OS to use SHA512 rather than yescrypt.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.099% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Fortra
Fortra boks |
|
| Vendors & Products |
Fortra
Fortra boks |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Insecure defaults in the Server Agent component of Fortra's Core Privileged Access Manager (BoKS) can result in the selection of weak password hash algorithms. This issue affects BoKS Server Agent 9.0 instances that support yescrypt and are running in a BoKS 8.1 domain. | |
| Title | Weak Password Hash in Core Privileged Access Manager (BoKS) | |
| Weaknesses | CWE-916 | |
| References |
| |
| Metrics |
cvssV3_1
|