CVE-2014-9471
NoneCVSS
—
EPSS
7.1%
Published
Jan 16, 2015
CISA due date
—
Cloudanix analysis
A problem in common date-handling tools can let attackers crash programs or potentially run their own code by feeding in specially formatted date text.
- Exploitation
- Remote Unauthenticated
- Attacker needs
- None
- Complexity
- Low
- Impact
- Remote Code Execution
- Component
- Library
- Class
- Memory Corruption
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
Memory corruption in parse_datetime allows crafted date strings to trigger crashes or arbitrary code execution when processed by date or touch commands.
Why it matters to the business
Legacy systems using affected coreutils packages face denial-of-service risks or potential compromise from remote input; the decade-old issue has stable low exploit probability and available public exploits but no ransomware or KEV usage.
How an attack unfolds
An attacker supplies a malicious date argument such as "--date=TZ=\"123\"345\" @1" to the date or touch command, exploiting the parsing flaw to corrupt memory. With exploit code publicly available since 2015, opportunistic attackers could target exposed CLI invocations or scripts processing untrusted input.
How to fix it
Upgrade affected packages to fixed versions: snappy (Chainguard/Wolfi), snappy-dev, snappy-doc, and snappy-static all fixed in version 0. Replace any vulnerable coreutils with current maintained builds and avoid processing attacker-controlled date strings.
How to confirm the fix worked
Confirm package versions match the listed fixed releases; test date and touch commands with known malicious strings to verify absence of crashes or unexpected behavior.
Typical attack path
- Locate systems exposing date or touch commands to untrusted input
- Craft malicious TZ or date string to trigger parse_datetime flaw
- Invoke command with crafted argument to cause memory corruption
- Achieve crash for DoS or attempt code execution via corrupted state
How to detect it
Search command execution logs and audit trails for date or touch invocations containing unusual TZ= or quoted date patterns; monitor for coreutils process crashes or segmentation faults tied to parse_datetime.
- --date=TZ="123"345" @1
- parse_datetime
- touch.*TZ=
- date.*crafted.*string
What your security team should do
- Immediately verify and enforce the fixed package versions across all environments
- Audit scripts and services that pass external input to date or touch commands
- Remove or sandbox legacy coreutils usage where possible given the 4308-day exposure window
The record
The parse_datetime function in GNU coreutils allows remote attackers to cause a denial of service (crash) or possibly execute arbitrary code via a crafted date string, as demonstrated by the "--date=TZ="123"345" @1" string to the touch or date command.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Debian:10 | coreutils | 0 | 8.23-1 |
| Debian:11 | coreutils | 0 | 8.23-1 |
| Debian:12 | coreutils | 0 | 8.23-1 |
| Debian:13 | coreutils | 0 | 8.23-1 |
| Mageia:4 | coreutils | 0 | 8.21-6.1.mga4 |
| Ubuntu:14.04:LTS | coreutils | 0 | 8.21-1ubuntu5.1 |
Related vulnerabilities
- CVE-2015-1865 fts.c in coreutils 8.4 allows local users to delete arbitrary files. Also affects coreutils
- CVE-2016-2781 chroot in GNU coreutils, when used with --userspec, allows local users to escape to the… Also affects coreutils
- CVE-2025-5278 A flaw was found in GNU Coreutils. Also affects coreutils
- CVE-2003-0853 An integer overflow in ls in the fileutils or coreutils packages may allow local users to… Also affects coreutils
- CVE-2015-4041 The keycompare_mb function in sort.c in sort in GNU Coreutils through 8.23 on 64-bit… Also affects coreutils
- CVE-2015-4042 Integer overflow in the keycompare_mb function in sort.c in sort in GNU Coreutils through… Also affects coreutils
- CVE-2009-4135 The distcheck rule in dist-check.mk in GNU coreutils 5.2.1 through 8.1 allows local users… Also affects coreutils