La histeria normal de cualquier adicto a Steam es comprensible cuando al parecer la base de datos de la compañía de tu preferencia parece tener una fuga en la seguridad de sus datos (los tuyos).
Con una base de usuarios rondando los 135 millones (confirmados 125 en febrero del 2015) la cosa no es cualquier moco de pavo. Pero aún así hay ocasiones donde la histeria parece ser la norma sin importar el tamaño de la falla.
En días pasados se reportaron algunos issues en la venta navideña de Steam. El pánico cundió de inmediato. Se reportaba varias fallas. Entre ellas la visualización de los datos de n número cuentas, cambio de idioma en el display (polaco, español, alemán, francés, etc.) y la posibilidad de compras inesperadas a cargo del saldo de cualquier afectado.
Había motivos para pensar que tus datos en Steam estaban comprometidos...pero también había indicativos de que no era precisamente un hack lo que le estaba ocurriendo a la plataforma. Una semana después tenemos la respuesta oficial y NO parcial de Steam.
Los declaraciones temporales de Steam referentes a la situación no hacían más que aumentar la histeria del colectivo.
De manera prudente Steam esperó hasta tener el dato completo de la situación. El comunicado oficial de Steam, hoy, vía Kotaku:
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.
No hay comentarios:
Publicar un comentario
Hola!