Print 33 comment(s) - last by JimKiler.. on Jul 16 at 2:22 PM

Fortunately passwords appear to have been strongly hashed

NVIDIA Corp. (NVDA) had some bad news to announce late yesterday.  The site posted the following statement on its Forums page:

NVIDIA suspended operations of the NVIDIA Forums ( last week.

We did this in response to suspicious activity and immediately began an investigation. We apologize that our continuing investigation is taking this long. Know that we are working around the clock to ensure that secure operations can be restored.

Our investigation has identified that unauthorized third parties gained access to some user information, including:

  • username
  • email address
  • hashed passwords with random salt value
  • public-facing "About Me" profile information
NVIDIA did not store any passwords in clear text. "About Me" optional profiles could include a user’s title, age, birthdate, gender, location, interests, email and website URL – all of which was already publicly accessible.

NVIDIA is continuing to investigate this matter and is working to restore the Forums as soon as possible. We are employing additional security measures to minimize the impact of future attacks.

All user passwords for our Forums will be reset when the system comes back online. At that time, an email with a temporary password, along with instructions on how to change it, will be sent to the user’s registered email address.

As a precautionary measure, we strongly recommend that you change any identical passwords that you may be using elsewhere.

NVIDIA does not request sensitive information by email. Do not provide personal, financial or sensitive information (including new passwords) in response to any email purporting to be sent by an NVIDIA employee or representative.

NVIDIA, like Sony Corp. (TYO:6758), Nokia Oyj. (HEX:NOK1V), and others likely fell victim to an SQL injection attack.  SQL injection attacks exploit the fact that internet user databases are publicly hosted and send them malformed request strings designed to execute disallowed commands.  They can be defeated by careful programming, but implementing protections is a time intensive and expensive process, hence many companies have vulnerable databases.

[Image Source: NVIDIA Wallpapers]

NVIDIA Forums is a popular stomping ground both for gaming enthusiasts and for programmers developing GPU applications using NVIDIA's proprietary CUDA API.

The first of two major concerns arising from the NVIDIA attack is the possibility of phishing.  Now that an unknown party has users emails, it could send them messages (as the NVIDIA post alludes to), trying to trick them into providing their password in plaintext or other personal details.

The second danger is the possibility that the hashed passwords could be cracked.  NVIDIA did not reveal what hashing algorithm it used, but the fact that it used a random salt value indicates that its passwords were likely relatively strongly hashed.

The announcement was actually the second major announcement of a SQL injection breach on Thursday.  Earlier, Yahoo! Inc. (YHOO) announced that hackers had found 453,000 of its user passwords.  Yahoo! was less fortunate than NVIDIA -- baffingly it decided to store its user passwords in plaintext, greatly increasing the potential damage to its users.

Source: NVIDIA Forums

Comments     Threshold

This article is over a month old, voting and posting comments is disabled

RE: Eventually
By Ammohunt on 7/13/2012 8:09:26 PM , Rating: 2
Exactly lazy devlopers and lazy systems guys leave stuff like this for the hackers to graze upon.

RE: Eventually
By Samus on 7/13/2012 11:38:33 PM , Rating: 3
It's long been my experience that 9/10 database developers know quite little about SQL, so I'd assume those hosting the databases know even less.

It really isn't that complicated. I took a SQL 2005 (v5.5) class at a community college nearly a decade ago and can still securely deploy and upgrade older databases to SQL 2008. Not much has changed, in fact, they've actually tightened it down since its introduction in Windows NT, forcing you to perform a secure deployment (unless you stick with legacy compatibility)

But as OP said, it isn't completely a SQL problem, it's the link (or LINQ) from another program that leaves the holes.

RE: Eventually
By NellyFromMA on 7/16/2012 10:22:22 AM , Rating: 2
It's more like more often than not companies would rather not revamp existing systems that sometiems are older than 10 years. hindsight is 20/20, but getting approval to correct a security loophole you weren't privy to as a community at the time or wasn't as much of an issue back them is not the easiest thing.

Esp if you have to get approval from shareholders at any given moment.

Don't get me wrong, fixing this stuff is essential... there's just reasons why it persists to this day and will for a few years more.

"This week I got an iPhone. This weekend I got four chargers so I can keep it charged everywhere I go and a land line so I can actually make phone calls." -- Facebook CEO Mark Zuckerberg

Most Popular ArticlesSmartphone Screen Protectors – What To Look For
September 21, 2016, 9:33 AM
UN Meeting to Tackle Antimicrobial Resistance
September 21, 2016, 9:52 AM
Walmart may get "Robot Shopping Carts?"
September 17, 2016, 6:01 AM
5 Cases for iPhone 7 and 7 iPhone Plus
September 18, 2016, 10:08 AM
Update: Problem-Free Galaxy Note7s CPSC Approved
September 22, 2016, 5:30 AM

Copyright 2016 DailyTech LLC. - RSS Feed | Advertise | About Us | Ethics | FAQ | Terms, Conditions & Privacy Information | Kristopher Kubicki