SANS ISC: Any other reports of decade change problems? - Internet Security | DShield

• SANS Site Network
  • Current Site
  • Internet Storm Center
  • Other SANS Sites Help
  • Graduate Degree Programs
  • Security Training
  • Security Certification
  • Security Awareness Training
  • Penetration Testing
  • Industrial Control Systems
  • Cyber Defense Foundations
  • DFIR
  • Software Security
  • Government OnSite Training

SANS ISC InfoSec Forums

How about non-technical? http://news.bbc.co.uk/2/hi/south_asia/8436186.stm

How about non-technical? http://news.bbc.co.uk/2/hi/south_asia/8436186.stm

Spamassassin had a similar regex looking for dates too far in the future: http://lwn.net/Articles/368396/

Do you have any pointers to the CSM load balancer issue? The documentation I've found indicates that the default is for the cookie to be a session cookie without a defined expiration.

One of the banks here is Australia had a strange problem with EFTPOS machines.... for some reason the date skipped fwd to 2016...

http://www.theaustralian.com.au/australian-it/computer-error-hits-bank-of-queensland/story-e6frgakx-1225815919308

A brief excerpt from Marcus Sach's Spamassasin post on 1/2/2010 reads "I thought we fixed all of these problems ten years ago when we went through the Y2K transition. " http://isc.sans.org/diary.html?storyid=7858

Unfortunately not, a lot of people made a lot of money delaying the problem by 10 years or more. Other common dates of 2030, 2031, and 2050 were used by coders who instead of changing years to 4 digits or more, simply used a slider window of if greater than xx then "19xx", else "20xx".

I railed against such short sightedness more than 10 years ago when I was coding. Those who disagreed said, the code will be obsolete and replaced by then. Hmm, isn't that why y2k was such a concern, code that was obsolete yet not replaced, in fact it had been replicated and ported into increasing numbers of application. Code reuse as it were.

* Home
* Trial Copies of SAP Software
* About

SAP Spool issue – affects all Releases
January 4th, 2010 Posted in Management, Monitoring, OSS, Support Pack

SAP have detected a problem in the spool area which affects all customers in the world regardless of the SAP release and any support package level.

As soon as the retention time of a spool request exceeds 2009/12/31 a wrong date 2100/01/01 is entered during creation of the spool request. As a consequence these spool requests will not be deleted anymore from the spool reorg jobs. Using the default retention period this affects all spool requests on each SAP system in the world created since 2009/12/23.
http://www.basissap.com/2010/01/sap-spool-issue-affects-all-releases/

Windows Mobile and maybe other cell phones are having issues. SMS messages sent in 2010 are being dated 2016. http://www.wmexperts.com/y2016-sms-bug

The Palm Pre WebOS seems to be having problems with its Exchange calendar sync feature: http://forums.palm.com/palm/board/message?board.id=webossoftware&thread.id=13247

Some German ATM cards are getting rejected due to an error in the security chip: http://www.h-online.com/security/news/item/Problems-obtaining-cash-from-German-ATMs-Update-894801.html

These may not be 2010 related and just AT&T being AT&T:

http://forums.e71fanatics.com/topic/at038t-new-years-crash

http://forums.macrumors.com/showthread.php?t=842481

If it was just network congestion, the one person's query in the second link about what would happen in a nationwide emergency is a bit sobering, particularly in light of AT&T's request to discontinue wired phone service altogether. It's effectively a DDoS from authorized users. http://gigaom.com/2009/12/30/att-to-fcc-let-my-landlines-go/

Even Web apps are vulnerable to this issue :)
http://community.invisionpower.com/index.php?app=tracker&showissue=20365
Users of Invision Power Board are unable to create new blog entries.

Symantec Endpoint Protection is having issues starting 12/31/2009 with virus definitions appearing to be out of date. May not be 2010 change related but...

http://www.symantec.com/connect/forums/official-status-sepm-definitions-stay-31-12-2009-last-updated-04-jan-2010

I read on a Danish website that Siemens park meters in Copenhagen haven't been working since January 1st! Confirmed by Siemens to be a "communication problem" between 2 units

I read on a Danish website that Siemens park meters in Copenhagen haven't been working since January 1st! Confirmed by Siemens to be a "communication problem" between 2 units

Issue with Tenable Security Center 3 (Nessus proxy). Tenable has an updated rpm package and hotfix. Scans will not run and error out as "Launch window exceeded"