mport bootstrap index fetch can continue after hash verification failure
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| MidnightBSD | mport | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Midnightbsd | Mport |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.218% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Midnightbsd
Midnightbsd mport |
|
| Vendors & Products |
Midnightbsd
Midnightbsd mport |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | mport is the MidnightBSD Package Manager. Prior to 2.7.8, the mport_fetch_bootstrap_index() function in libmport/fetch.c could return success when bootstrap index hash verification encountered a missing or invalid hash because the failure path did not preserve a fatal result. A network attacker or compromised mirror able to alter bootstrap index content or its transport path could therefore cause mport to proceed with an unverified or tampered bootstrap package index. This issue is fixed in version 2.7.8. | |
| Title | mport bootstrap index fetch can continue after hash verification failure | |
| Weaknesses | CWE-345 CWE-347 |
|
| References |
|
|
| Metrics |
cvssV4_0
|