Skip to content

GHSA-532v-xp3f-837c

Duplicate Advisory: uutils coreutils has an Incorrect Provision of Specified Functionality Issue in its cut Utility

Low Withdrawn Jul 6, 2026 crates.io
Severity
3.3 / 10
Low · CVSS 3.1
Exploit chance (EPSS)
—
No score published
Known exploited
No
Not in CISA's catalog
Weakness
CWE-684 Incorrect Provision of Specified Functionality
Fix
0.8.0
Upgrade coreutils to this version or later

Description

Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-pmfc-4wjj-gmhx. This link is maintained to preserve external references.

Original Description

A logic error in the cut utility of uutils coreutils causes the utility to ignore the -s (only-delimited) flag when using the -z (null-terminated) and -d '' (empty delimiter) options together. The implementation incorrectly routes this specific combination through a specialized newline-delimiter code path that fails to check the record suppression status. Consequently, uutils cut emits the entire record plus a NUL byte instead of suppressing it. This divergence from GNU coreutils behavior creates a data integrity risk for automated pipelines that rely on cut -s to filter out undelimited data.

Affected versions

crates.io

PackageVulnerableFixed in
coreutils
< 0.8.0
0.8.0

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

coreutils crates.io → 0.8.0

cargo
cargo update -p coreutils --precise 0.8.0

Severity breakdown

CVSS 3.1 3.3

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

Weakness

CWE-684: Incorrect Provision of Specified Functionality

The code does not function according to its published specifications, potentially leading to incorrect usage.

How to prevent it
  • Implementation: Ensure that your code strictly conforms to specifications.

References

Timeline

  1. Published
  2. Withdrawn
  3. Last updated by the source
AdvisorySeverityWhy it's related
GHSA-m2pg-c7m6-77pj
uutils coreutils has an Improper Input Validation Issue in its cut Utility
Medium Also affects coreutils
GHSA-fhr3-xh3q-69w6
uutils coreutils has an Incorrect Provision of Specified Functionality Issue
Low Also affects coreutils
GHSA-5pv5-xh52-hvrp
uutils coreutils has an Incorrect Short Circuit Evaluation Issue
Low Also affects coreutils
GHSA-5v4g-vw9x-h534
uutils coreutils has an Improper Input Validation Issue in its env Utility
Low Also affects coreutils
GHSA-6g8r-74qp-6859
uutils coreutils has a Time-of-check Time-of-use (TOCTOU) Race Condition
Medium Also affects coreutils
GHSA-vx9m-xjwf-8cqm
uutils coreutils has an Improper Handling of Unicode Encoding Issue
Low Also affects coreutils
GHSA-4wrp-79m8-9m9p
uutils coreutils has a Time-of-check Time-of-use (TOCTOU) Race Condition
Medium Also affects coreutils
GHSA-wq63-vh5h-pr5p
uutils coreutils has a UNIX Symbolic Link (Symlink) Following issue
Medium Also affects coreutils
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor