ZDNet UK


Skip to Main Content

ZDNet.co.uk - Winner of Best Business Website 2007
  1. Home
  2. News
  3. Blogs
  4. Reviews
  5. Prices
  6. Resources
  7. Community
  8. My ZDNet

 

ZDNet UK RSS Feeds


IT Jobs

Security threats Toolkit

New website tracks zero-day flaws

Joris Evers CNET News.com

Published: 06 Dec 2006 09:41 GMT

  • Email
  • Trackback
  • Clip Link
  • Print friendly
  • Post Comment

eEye Digital Security has launched a website that tracks publicly released security bugs that don't have an official patch, also known as zero-day flaws.

The new eEye Zero-Day Tracker website on Tuesday listed seven zero-day vulnerabilities, six of which affect Microsoft software and one related to Adobe Systems' Acrobat. For each of the problems, eEye suggests steps people can take to protect against exploitation of the flaws.

"More zero-day security vulnerabilities and attacks are being discovered every day," Marc Maiffret, eEye's chief technology officer, said in a statement. "We've been overwhelmed by requests from our customers to give them the information and time they need to protect their networks."

Security monitoring companies Secunia and the French Security Incident Response Team, or FrSIRT, also track unpatched flaws. However, these companies don't offer a simple overview of all zero-days. Secunia lists them by product, for example.

There has been an apparent increase this year in the use of new, yet-to-be-patched flaws in targeted cyberattacks. Cybercrooks have found that they could take advantage of Microsoft's monthly patch cycle by timing new attacks right after the software maker releases its fixes.

Microsoft's patch day is on the second Tuesday of each month, and the company doesn't break its cycle unless an attack has a widespread impact. As a result, security experts have coined the term "Zero-day Wednesdays".

Flaws in Office applications especially seem to be favoured by the bad guys. Microsoft and security companies have repeatedly had to issue warnings this year about new, small-scale attacks that exploit yet-to-be-plugged security holes in applications such as Word, PowerPoint and Excel.

  • Email
  • Trackback
  • Clip Link
  • Print friendly Print with HP

Did you find this article useful?
240 out of 307 people found this useful


Full Talkback thread

0 comments

Company/Topic Alerts

Create a new alert from the list below:





Related Jobs

.NET Architect Contract - Stoke-on-Trent

NET Platform knowledge - Web architecture experience - Security procedures experience with large scale Websites and their vulnerabilities Please ...

Java Developer. Learn Ruby! North London. 30,000 - 40,000

A financial services website are looking to recruit a developer with excellent programming skills. You will be working on a high traffic busy website ...

Flex Developer - Adobe Flex, ActionScript 3.0 - Central London

One of Huxley Associates media clients is urgently seeking a Flex developer to join their team for a 3 month contract. You will work on a number of ...

Sentry Posts Blog

www.globlefashion.com Tiffany wholesal...

www.globlefashion.com Tiffany wholesale, wholesale Tiffany, bvlgari jewelry www.globlefashion.com,Tiffany jewelry,Gucci jewelry,Tiffany&co www.globlefashion.com ,18K GOLD Tiffany... More

5 comments

How many headshots does one chairperso...

We got a strange request last week from the head of PR from Russian security experts Kaspersky. It seems although the company was very happy with the interview we recently carried with... More

Post a comment

Google sponsors open source security p...

Google has announced it is to sponsor oCERT, an open source computer emergency response team. In a blog post on Monday, Google security engineer Will Drewry said that one of the... More

Post a comment

Featured Talkback

On the contrary, if vendors were forced to stand behind their products it should increase innovation. It would force more, and better , testing before hitting the sales floor, resulting in fewer updates and less downtime for the consumer. At present the EULA removes responsibility from the vendor, and moves it to the user, which is a step backward. Make the vendor responsibility for their code.

By: ator1940

Read full story:
RSA: Vendor liability may stifle innovation