Home | Blog | Software | Reviews and Features | Forum | Help | Donate | About us

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • October 22, 2016, 06:34:24 PM
  • Proudly celebrating 10 years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Author Topic: Steam has a leak... sort of...  (Read 483 times)


  • Supporting Member
  • Joined in 2006
  • **
  • Posts: 8,341
  • "In my dreams, I always do it right."
    • View Profile
    • Donate to Member
Steam has a leak... sort of...
« on: December 31, 2015, 03:36:41 PM »
Christmas is a good time and a bad time for Steam.  They sell a lot.  But just like XBoxLive and PSN, they come under attacks by hackers trying to communicate... something.  Or maybe just to watch the world burn?

This Christmas was no different on that regard.  But Valve's failover strategy was not quite good- and gave the impression that they'd been hacked.

From: http://store.steampo...19852/?snr=1_550_552

On December 25th, a configuration error resulted in some users seeing Steam Store pages generated for other users. Between 11:50 PST and 13:20 PST store page requests for about 34k users, which contained sensitive personal information, may have been returned and seen by other users.

The content of these requests varied by page, but some pages included a Steam user’s billing address, the last four digits of their Steam Guard phone number, their purchase history, the last two digits of their credit card number, and/or their email address. These cached requests did not include full credit card numbers, user passwords, or enough data to allow logging in as or completing a transaction as another user.

If you did not browse a Steam Store page with your personal information (such as your account page or a checkout page) in this time frame, that information could not have been shown to another user.

Valve is currently working with our web caching partner to identify users whose information was served to other users, and will be contacting those affected once they have been identified. As no unauthorized actions were allowed on accounts beyond the viewing of cached page information, no additional action is required by users.

Continued at link, brought courtesy of Ghacks.