Threat Update | Leap Second June 30, 2015
The term “Leap Second” was coined to reflect that the last minute of June 30th will be one second longer than a standard minute, meaning that June 30, 2015 23:59:60 will be a valid and correct time. This time could cause potential issues across various IT infrastructures.
It has been speculated that the Leap Second could cause a server hang or excessive CPU usage. In this scenario the server could become unresponsive or the java applications could start to leverage 100% CPU, as the leap second would cause the futex to repeatedly time out.
Additionally, rules with time stamps between 0 – 59 may fail as a result of the 60 second notation. Any OS could be affected by this rule breaking.
Herjavec Group is actively monitoring this situation but has not received any updates or alerts from our technology partners or customers to date. We will communicate any recommended proactive measures in a timely manner.