mport package installation can overwrite existing unmanaged or differently owned files
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.554% 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, package installation lacked a preflight check for incoming non-directory assets that already existed on disk. The affected logic across libmport/check_preconditions.c, libmport/install_primative.c, and libmport/mport_private.h did not apply MPORT_PRECHECK_FILE_CONFLICTS, so a crafted or conflicting package could overwrite a file owned by another package or unmanaged by mport. The check is bypassed only when the operator explicitly enables mport->force. Privileged installation without that override could compromise local filesystem integrity and package database consistency. This issue is fixed in version 2.7.8. | |
| Title | mport package installation can overwrite existing unmanaged or differently owned files | |
| Weaknesses | CWE-668 CWE-73 |
|
| References |
| |
| Metrics |
cvssV4_0
|