Steam Hesap Sorunları - 25/12/15

[GokTuRK]

Yine mi?

[batuhan]

2002 de kayıt olurken öyle almışım kaldı :)

[Xeph]

olm hiçbişey olmamış lan, amma curcuna yapmışlar redditde falan

totalbiscuit başınıza gelebilcek en kötü şey email adresinize pishing spamlanması olur diyor huehue

[Seru]

Killer said:

bu arada ben estonyadayım tl görüyorum oyunları. bu dalgaya yeni mi geçtiler localde nerde kayıt yaptırdyısan onun parasını görme falan? harbi euro olarak göçertiyodu bazı oyunların fiyatı

para kısmına tıkla oradan ülke seç. estonya seçersen liraya bay bay de geri gelmez.

[Killer]

yok aman asd

[Sam]

update on xmas issues

said:

We'd like to follow up with more information regarding Steam's troubled Christmas.

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.

[Anhora]

Markette gezinirken ikide bir atmaya başladı. Her seferinde steam guardla login olmaktan gına geldi gaben.

[Madcat]

Böyle bir mail geldi az önce bu olayla ilgili:

Valve'den e-mail

Dear Steam User,

As you may know, for a brief period on December 25th, a configuration error resulted in some Steam users seeing incorrectly cached Steam Store pages generated for other Steam users. If you are not familiar with the issue, an overview of what happened is available at http://store.steampowered.com/news/19852/ .

If you accessed the Steam Store between 11:50 PST and 13:20 PST on December 25th, your account could have been affected by this issue. If you did not use the Steam Store during that time, your account was not affected.

Between the times above, a requested web page for information about your Steam account may have been incorrectly displayed to another Steam user in your local area. This page may have included your email address, country, purchase history and last 4 digits of your phone number if one was associated with your account. It may have also included the last two digits of a credit card number or a PayPal email address, if previously saved for future purchases. It did not include full credit card numbers, Steam account passwords, or other information that would allow another user to complete a transaction with your billing information.

We are contacting you because an IP address previously used by your account to access Steam made a web page request as described above. Because IP addresses are commonly shared for home networks, mobile devices and by internet providers, we are unable to verify that your account was actually the one that made this request. For example one affected IP address was previously used by over 1,700 Steam accounts. Consequently we are notifying all users who have previously used this IP address.

This event did not make it possible to compromise your Steam account or make a fraudulent transaction from your account, but we want you to be aware of what information could have been seen by another Steam user.

We're sorry this happened and have taken steps to prevent this problem from occurring in the future.

If you used the store between 11:50 PST and 13:20 PST on December 25th and you have questions please email [email protected].

- Valve