Yahoo! closes security hole

Powered by SC Magazine
 

Promises to beef up security after password breach.

Yahoo has fixed a security vulnerability that allowed hackers to seize roughly 450,000 unencrypted email addresses and passwords belonging to members of its content-sharing platform.

In a blog post, the web giant said the intruders accessed a "standalone file" that contained the login data used by writers who joined Associated Content  prior to May 2010, the month when Yahoo acquired the company for $US100 million.

Now called Yahoo Contributor Network, the business unit specialises in producing freelancer-generated, search-optimised content.

According to experts, the hackers, which claimed to be part of a relatively unknown contingent known as "D33ds Company," obtained the information in clear text through a SQL injection attack, a common technique used to infiltrate vulnerable web applications.

"We have taken swift action and have now fixed this vulnerability, deployed additional security measures for affected Yahoo users, enhanced our underlying security controls and are in the process of notifying affected users," the post said.

"In addition, we will continue to take significant measures to protect our users and their data."

The company declined to specify further.

Affected users will be asked to answer a series of challenge questions to enable them to reset their credentials.

This article originally appeared at scmagazineus.com

Copyright © SC Magazine, US edition


Yahoo! closes security hole
 
 
 
Top Stories
Earning the right to innovate
Breaking down the barriers to innovation is a long, but rewarding process, says Bank of Queensland Group CIO, Julie Bale.
 
A call for timely reporting
[Blog post] Businesses need incentives to keep customer data secure.
 
Doubts cast on Queensland's ICT Dashboard
Opposition, former Govt CIO say it can't be trusted.
 
 
Sign up to receive iTnews email bulletins
   FOLLOW US...
Latest Comments
Polls
What is delaying adoption of public cloud in your organisation?







   |   View results
Lock-in concerns
  26%
 
Application integration concerns
  3%
 
Security and compliance concerns
  29%
 
Unreliable network infrastructure
  9%
 
Data sovereignty concerns
  22%
 
Lack of stakeholder support
  3%
 
Protecting on-premise IT jobs
  5%
 
Difficulty transitioning CapEx budget into OpEx
  3%
TOTAL VOTES: 857

Vote