Steam - Update on Christmas Issues

[HiddenX]

What happened on the Christmas Steam Sale? - here's an update:

What happened

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.

How it happened

Early Christmas morning (Pacific Standard Time), the Steam Store was the target of a DoS attack which prevented the serving of store pages to users. Attacks against the Steam Store, and Steam in general, are a regular occurrence that Valve handles both directly and with the help of partner companies, and typically do not impact Steam users. During the Christmas attack, traffic to the Steam store increased 2000% over the average traffic during the Steam Sale.

In response to this specific attack, caching rules managed by a Steam web caching partner were deployed in order to both minimize the impact on Steam Store servers and continue to route legitimate user traffic. During the second wave of this attack, a second caching configuration was deployed that incorrectly cached web traffic for authenticated users. This configuration error resulted in some users seeing Steam Store responses which were generated for other users. Incorrect Store responses varied from users seeing the front page of the Store displayed in the wrong language, to seeing the account page of another user.

Once this error was identified, the Steam Store was shut down and a new caching configuration was deployed. The Steam Store remained down until we had reviewed all caching configurations, and we received confirmation that the latest configurations had been deployed to all partner servers and that all cached data on edge servers had been purged.

We will continue to work with our web caching partner to identify affected users and to improve the process used to set caching rules going forward. We apologize to everyone whose personal information was exposed by this error, and for interruption of Steam Store service.

More information.

 

[Lucky Day]

A strange thought came to my head. Maybe they were worried this year about the kind of traffic a decent steam sale would have brought them this holiday, that it would have caused this sort of thing.

 

[Wisdom]

Just one of the reasons Steam knows little about me.
No CC info, no Phone number, no linked accounts. Nada.
Its very transactional every purchase and I store nothing.

Now do they have all this information stored somewhere? Being steam I'm sure they have my browser history saved somewhere. But the optional stuff... its always nope.

 

[you]

As they said in their detail announcement. What happened is their caching partner made a mistake when they changed a configuration to address a D:OS attack. They (valve) did not make this mistake and their site was not hacked. It would be good for folks commenting to read up on caching (cdn's) and how they work so you have an understanding of what happened.

Most of the major sites (including banks) use caching partner and these sort of mistakes can happen (though hopefully the caching partners will do a better job in the future (i.e, learn from this mistake).

A strange thought came to my head. Maybe they were worried this year about the kind of traffic a decent steam sale would have brought them this holiday, that it would have caused this sort of thing.

 

[Wisdom]

Also, it was a bit weird to log in, see the language all in Russian and no games that were recognizable on the left hand side. Apparently whoevers cache I was seeing was a serious gamer as there was pages and pages and pages of games on the left.

 

[Zloth]

There's an easter egg mystery floating around the Steam sale, too: http://www.pcgamer.com/something-strange-is-afoot-in-the-steam-winter-sale/

 

[HiddenX]

After creating a few mystery badges - I got this on my profile:

 

[Aubrielle]

Aww...they gave your curator group back to you...wrapped up all nice with a bow...?