date returns "invalid date" for some timezone's DST
Bug #354793 reported by
Alexandre Martani
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apt (Ubuntu) |
Fix Released
|
High
|
Michael Vogt | ||
Dapper |
Fix Released
|
High
|
Jamie Strandboge | ||
Gutsy |
Won't Fix
|
High
|
Jamie Strandboge | ||
Hardy |
Fix Released
|
High
|
Jamie Strandboge | ||
Intrepid |
Fix Released
|
High
|
Jamie Strandboge | ||
Jaunty |
Fix Released
|
High
|
Michael Vogt | ||
coreutils (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned | ||
Dapper |
Won't Fix
|
Undecided
|
Unassigned | ||
Gutsy |
Won't Fix
|
Undecided
|
Unassigned | ||
Hardy |
Won't Fix
|
Undecided
|
Unassigned | ||
Intrepid |
Won't Fix
|
Undecided
|
Unassigned | ||
Jaunty |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Date command gives an error when trying to get a day that starts the daylight saving time. Examples:
$ date --date=2008-10-18
Sáb Out 18 00:00:00 BRT 2008
$ date --date=2008-10-19
date: data inválida "2008-10-19"
$ date --date=2008-10-20
Seg Out 20 00:00:00 BRST 2008
$ date --date=2009-10-17
Sáb Out 17 00:00:00 BRT 2009
$ date --date=2009-10-18
date: data inválida "2009-10-18"
$ date --date=2009-10-19
Seg Out 19 00:00:00 BRST 2009
I checked this as a security bug as this can cause scripts to fail. For example, cron's apt script fails if update-stamp is in this day, causing the system to never more update periodically. In other words: Many servers can be out of date because of this bug.
Related branches
CVE References
Changed in apt (Ubuntu): | |
status: | New → Confirmed |
Changed in coreutils (Ubuntu): | |
status: | Incomplete → Confirmed |
Changed in apt (Ubuntu): | |
importance: | Undecided → High |
summary: |
- date error on saving time starting day + date returns "invalid date" for some timezone's DST |
Changed in coreutils (Ubuntu Dapper): | |
status: | New → Won't Fix |
Changed in coreutils (Ubuntu Gutsy): | |
status: | New → Won't Fix |
Changed in coreutils (Ubuntu Hardy): | |
status: | New → Won't Fix |
Changed in coreutils (Ubuntu Intrepid): | |
status: | New → Won't Fix |
Changed in apt (Ubuntu Dapper): | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Jamie Strandboge (jdstrand) |
Changed in apt (Ubuntu Gutsy): | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Jamie Strandboge (jdstrand) |
Changed in apt (Ubuntu Hardy): | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Jamie Strandboge (jdstrand) |
Changed in apt (Ubuntu Intrepid): | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Jamie Strandboge (jdstrand) |
Changed in apt (Ubuntu Jaunty): | |
assignee: | nobody → mvo |
To post a comment you must log in.
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.