uutils coreutils split Local Data Integrity Issue via Lossy Filename Encoding
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Uutils | coreutils | unaffected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Uutils | Coreutils |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-vx9m-xjwf-8cqm | uutils coreutils has an Improper Handling of Unicode Encoding Issue |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.143% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:uutils:coreutils:*:*:*:*:*:rust:*:* |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Uutils
Uutils coreutils |
|
| Vendors & Products |
Uutils
Uutils coreutils |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A logic error in the split utility of uutils coreutils causes the corruption of output filenames when provided with non-UTF-8 prefix or suffix inputs. The implementation utilizes to_string_lossy() when constructing chunk filenames, which automatically rewrites invalid byte sequences into the UTF-8 replacement character (U+FFFD). This behavior diverges from GNU split, which preserves raw pathname bytes intact. In environments utilizing non-UTF-8 encodings, this vulnerability leads to the creation of files with incorrect names, potentially causing filename collisions, broken automation, or the misdirection of output data. | |
| Title | uutils coreutils split Local Data Integrity Issue via Lossy Filename Encoding | |
| Weaknesses | CWE-176 | |
| References |
| |
| Metrics |
cvssV3_1
|