mport verify can compare stale checksum data after hashing failures
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.113% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Midnightbsd
Midnightbsd mport |
|
| Vendors & Products |
Midnightbsd
Midnightbsd mport |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | mport is the MidnightBSD Package Manager. Prior to 2.7.8, mport_verify_package() in libmport/verify.c could continue after MD5File() or SHA256_File() failed and compare an expected checksum with stale data in the hash buffer rather than a newly computed digest. An attacker able to influence an installed file or the conditions that make hashing fail could receive a misleading integrity result or hide a checksum failure. This issue is fixed in version 2.7.8. | |
| Title | mport verify can compare stale checksum data after hashing failures | |
| Weaknesses | CWE-354 CWE-755 |
|
| References |
| |
| Metrics |
cvssV4_0
|