Duplicate Advisory: uutils coreutils incorrectly handles exit codes when processing multiple files
### Duplicate Advisory This advisory has been withdrawn because it is a duplicate of GHSA-4x34-chg5-mwjj. This link is maintained to preserve external references. ### Original Description The recursive mode (-R) of the chmod utility in uutils coreutils incorrectly handles exit codes when processing multiple files. The final return value is determined solely by the success or failure of the last file processed. This allows the command to return an exit code of 0 (success) even if errors were encountered on previous files, such as 'Operation not permitted'. Scripts relying on these exit codes may proceed under a false sense of success while sensitive files remain with restrictive or incorrect permissions.
AI Analysis
Technical Summary
In uutils coreutils' chmod utility, recursive mode (-R) does not aggregate error statuses across multiple files. Instead, it returns the exit code of the last processed file only. Consequently, if errors such as 'Operation not permitted' occur on earlier files, these are not reflected in the final exit code, misleading automation or scripts that depend on accurate exit codes for error handling. This behavior affects versions prior to 0.6.0 and is classified under CWE-253 (Incorrect Check of Function Return Value).
Potential Impact
Scripts or automated processes that rely on chmod's exit codes to verify successful permission changes may proceed under false assumptions of success. This can result in sensitive files retaining incorrect or overly restrictive permissions, potentially impacting system configuration or security posture. There is no direct confidentiality or availability impact reported, but the integrity of permission settings is affected.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no patch or official fix information is provided, users should verify permissions manually after recursive chmod operations or avoid relying solely on exit codes for error detection until a fix is available.
Duplicate Advisory: uutils coreutils incorrectly handles exit codes when processing multiple files
Description
### Duplicate Advisory This advisory has been withdrawn because it is a duplicate of GHSA-4x34-chg5-mwjj. This link is maintained to preserve external references. ### Original Description The recursive mode (-R) of the chmod utility in uutils coreutils incorrectly handles exit codes when processing multiple files. The final return value is determined solely by the success or failure of the last file processed. This allows the command to return an exit code of 0 (success) even if errors were encountered on previous files, such as 'Operation not permitted'. Scripts relying on these exit codes may proceed under a false sense of success while sensitive files remain with restrictive or incorrect permissions.
CVSS v3.1
Score 5.5medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In uutils coreutils' chmod utility, recursive mode (-R) does not aggregate error statuses across multiple files. Instead, it returns the exit code of the last processed file only. Consequently, if errors such as 'Operation not permitted' occur on earlier files, these are not reflected in the final exit code, misleading automation or scripts that depend on accurate exit codes for error handling. This behavior affects versions prior to 0.6.0 and is classified under CWE-253 (Incorrect Check of Function Return Value).
Potential Impact
Scripts or automated processes that rely on chmod's exit codes to verify successful permission changes may proceed under false assumptions of success. This can result in sensitive files retaining incorrect or overly restrictive permissions, potentially impacting system configuration or security posture. There is no direct confidentiality or availability impact reported, but the integrity of permission settings is affected.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no patch or official fix information is provided, users should verify permissions manually after recursive chmod operations or avoid relying solely on exit codes for error detection until a fix is available.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-vp6q-mv9j-j428
- Osv Schema Version
- 1.4.0
- Aliases
- []
- Ecosystems
- ["crates.io"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a4c341e27e9c797195f8ecf
Added to database: 07/06/2026, 23:02:54 UTC
Last enriched: 07/06/2026, 23:20:49 UTC
Last updated: 07/31/2026, 12:27:30 UTC
Views: 33
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.