This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "OWASP Game Security Framework Project"
Jason Haddix (talk | contribs) |
(→Collaboration) (Tag: Visual edit) |
||
(25 intermediate revisions by 2 users not shown) | |||
Line 4: | Line 4: | ||
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | {| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | ||
− | | valign="top" | + | | valign="top" style="border-right: 1px dotted gray;padding-right:25px;" | |
==OWASP Game Security Framework (GSF)== | ==OWASP Game Security Framework (GSF)== | ||
Line 12: | Line 12: | ||
'''The OWASP Game Security Framework (GSF) represents a modular approach to understanding the security issues that surround video game ecosystems.''' | '''The OWASP Game Security Framework (GSF) represents a modular approach to understanding the security issues that surround video game ecosystems.''' | ||
+ | In 2016 the videogame market became 99.6 Billion dollar industry... any why shouldn't it be? Some of the most prolific and complex software developed today are video games. They are professionally played, sponsored, scrutinized, monetized, and celebrated, just like many sports. They handle clients, servers, web components, monetary transfers, social interactions, virtual markets, etc, with every bit the need of security that most internet hosted apps have (if not more in some cases). The GSF is designed to help threat model gaming issues that have devastated new games. Most importantly we hope the GSF can help new developers and security testers alike root out bugs in your favorite titles. | ||
''The framework is broken into three main concepts / sections:'' | ''The framework is broken into three main concepts / sections:'' | ||
Line 20: | Line 21: | ||
''Components include the following:'' | ''Components include the following:'' | ||
− | |||
* '''Attack Surfaces''': the various surface areas that can be attacked by attackers in order to cause harm to the gaming ecosystem. | * '''Attack Surfaces''': the various surface areas that can be attacked by attackers in order to cause harm to the gaming ecosystem. | ||
Line 36: | Line 36: | ||
''Example:'' | ''Example:'' | ||
− | + | : "The attacker attacked and edited the <code>LOCAL GAME CLIENT (Attack Surface)</code>, which had a <code>LACK OF CLIENT INTEGRITY CONTROLS (Vulnerability)</code>, which allowed her to <code>ARTIFICIALLY INCREASE HER ABILITIES (Attacker Goal)</code>, ultimately leading to an <code>UNHAPPY PLAYER BASE (Negative Outcome)</code> and <code>DECLINING GAME REVENUE (Negative Outcome)</code> , which could have been prevented by <code>DEFENSE.</code>” | |
− | : "The attacker attacked and edited the <code>LOCAL GAME CLIENT (Attack Surface)</code>, which had a <code>LACK OF CLIENT INTEGRITY CONTROLS (Vulnerability)</code>, which allowed her to <code>ARTIFICIALLY INCREASE HER ABILITIES (Attacker Goal)</code>, ultimately leading to an <code>UNHAPPY PLAYER BASE (Negative Outcome)</code> and <code>DECLINING GAME REVENUE (Negative Outcome)</code> | ||
Line 48: | Line 47: | ||
The OWASP Game Security Framework is free to use. It is licensed under the http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one. | The OWASP Game Security Framework is free to use. It is licensed under the http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one. | ||
− | |||
{{Social Media Links}} | {{Social Media Links}} | ||
− | | valign="top" | + | | valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" | |
== What is the OWASP Game Security Framework? == | == What is the OWASP Game Security Framework? == | ||
Line 72: | Line 70: | ||
== Contributors == | == Contributors == | ||
− | * | + | * Kevin Hemmingsen |
+ | * Troy Cunefare | ||
+ | * Ryan Lawrence | ||
+ | * Martin Mendoza | ||
+ | * Koray Algan | ||
+ | * Tom Simkovic | ||
+ | * Matt Espinoza | ||
+ | * Chad Lynch | ||
== Related Projects == | == Related Projects == | ||
Line 79: | Line 84: | ||
* [[OWASP_Mobile_Security_Project|OWASP Mobile Security]] | * [[OWASP_Mobile_Security_Project|OWASP Mobile Security]] | ||
− | | valign="top" | + | | valign="top" style="padding-left:25px;width:200px;" | |
== Collaboration == | == Collaboration == | ||
Line 89: | Line 94: | ||
== News and Events == | == News and Events == | ||
− | * | + | * January, 2017: Doing a complete redesign of the project. |
+ | * March 2017: Presenting version 1.0 at HouSecCon 2017. | ||
==Classifications== | ==Classifications== | ||
Line 95: | Line 101: | ||
{| width="200" cellpadding="2" | {| width="200" cellpadding="2" | ||
|- | |- | ||
− | | align="center" valign="top" width="50% | + | | rowspan="2" align="center" valign="top" width="50%" | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]] |
− | | align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=]] | + | | align="center" valign="top" width="50%" | [[File:Owasp-builders-small.png|link=]] |
|- | |- | ||
− | | align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=]] | + | | align="center" valign="top" width="50%" | [[File:Owasp-defenders-small.png|link=]] |
|- | |- | ||
− | | colspan="2" align="center" | + | | colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]] |
|- | |- | ||
− | | colspan="2" align="center" | + | | colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]] |
|} | |} | ||
|} | |} | ||
− | = | + | = Attack Surfaces = |
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div> | <div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div> | ||
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | {| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | ||
− | | valign="top" | + | | valign="top" style="border-right: 1px dotted gray;padding-right:25px;" | |
− | == | + | == Attack Surfaces == |
The following is a list of the attack surfaces that can be found in video games of various types. | The following is a list of the attack surfaces that can be found in video games of various types. | ||
− | + | {| class="wikitable" border="1" style="text-align: left" | |
− | {| | ||
! Attack Surface | ! Attack Surface | ||
! Description | ! Description | ||
|- | |- | ||
| '''Local Game Client''' | | '''Local Game Client''' | ||
− | | | + | |The locally running game client that is accessible to the gamer because it's running on his/her machine. |
− | |||
|- | |- | ||
| '''Game Network Traffic''' | | '''Game Network Traffic''' | ||
− | | | + | |The network which game traffic traverses in order to reach the game's server or peers who are playing the game. |
− | |||
|- | |- | ||
| '''Game Server''' | | '''Game Server''' | ||
− | | | + | |The game server that is hosting the instance that gamers connect to in order to play the game. |
− | |||
|- | |- | ||
| '''Game Economy''' | | '''Game Economy''' | ||
− | | | + | |The economic system that exists within the game. |
− | + | |- | |
+ | |'''Game Mechanics''' | ||
+ | |The physics engine, logic, and other environmental components within the game. | ||
|- | |- | ||
|} | |} | ||
− | |||
{{Social Media Links}} | {{Social Media Links}} | ||
− | | valign="top" | + | | valign="top" style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right:25px;" | |
== What is the Attack Surfaces Section? == | == What is the Attack Surfaces Section? == | ||
Line 150: | Line 153: | ||
This section provides an overview of the various places an attacker can target to harm a given game infrastructure. | This section provides an overview of the various places an attacker can target to harm a given game infrastructure. | ||
− | == | + | == Sub-project Leader == |
* Daniel Miessler | * Daniel Miessler | ||
Line 170: | Line 173: | ||
|} | |} | ||
− | = | + | = Vulnerabilities = |
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div> | <div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div> | ||
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | {| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | ||
− | | valign="top" | + | | valign="top" style="border-right: 1px dotted gray;padding-right:25px;" | |
== Game Security Vulnerabilities == | == Game Security Vulnerabilities == | ||
Line 181: | Line 184: | ||
The following is a list of the vulnerabilities that can be found in video games of various types, and the attack surfaces they're likely to be associated with. | The following is a list of the vulnerabilities that can be found in video games of various types, and the attack surfaces they're likely to be associated with. | ||
− | {| | + | {| class="wikitable" border="1" style="text-align: left" |
! Attack Surface | ! Attack Surface | ||
! Vulnerability Name | ! Vulnerability Name | ||
Line 217: | Line 220: | ||
|} | |} | ||
− | |||
{{Social Media Links}} | {{Social Media Links}} | ||
− | | valign="top" | + | | valign="top" style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right:25px;" | |
== What is the Game Security Vulnerabilities Project? == | == What is the Game Security Vulnerabilities Project? == | ||
Line 226: | Line 228: | ||
The Security Vulnerabilities Project provides information on what types of vulnerabilities exist within games, and which attack surfaces they fall under. | The Security Vulnerabilities Project provides information on what types of vulnerabilities exist within games, and which attack surfaces they fall under. | ||
− | == | + | == Sub-project Leader == |
* Jason Haddix | * Jason Haddix | ||
+ | |||
+ | == Related Projects == | ||
+ | |||
+ | * [[OWASP_Mobile_Security_Project|OWASP Mobile Security]] | ||
+ | * [[OWASP_Top_Ten_Project|OWASP Web Top 10]] | ||
+ | |||
+ | == Collaboration == | ||
+ | [https://game-security.slack.com The Slack Channel] | ||
+ | |||
+ | == Resources == | ||
+ | * [https://www.owasp.org/index.php/Top_IoT_Vulnerabilities Top 10 IoT Vulnerabilities from 2014] | ||
+ | |||
+ | == News and Events == | ||
+ | * Coming Soon | ||
+ | |||
+ | |} | ||
+ | |||
+ | = Exploits = | ||
+ | |||
+ | <div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div> | ||
+ | |||
+ | {| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | ||
+ | | valign="top" style="border-right: 1px dotted gray;padding-right:25px;" | | ||
+ | |||
+ | == Exploits == | ||
+ | |||
+ | This list refers to what a given attacker might use to take advantage of a given bug within the game. | ||
+ | |||
+ | {| class="wikitable" border="1" style="text-align: left" | ||
+ | ! Exploit | ||
+ | ! Description | ||
+ | |- | ||
+ | | '''DDoS''' | ||
+ | |Force a player to DC, or attack the game itself so that it cannot serve customers. | ||
+ | |- | ||
+ | | '''Client Modification''' | ||
+ | |Modify the client in a way that gives advantage. | ||
+ | |- | ||
+ | | '''Malicious Macros''' | ||
+ | |Implementation of macros that perform unwanted actions. | ||
+ | |- | ||
+ | | '''Social Engineering''' | ||
+ | |Getting a player, mod, or game staff member to perform an action that helps the attacker. | ||
+ | |- | ||
+ | | '''Use Physics Bug''' | ||
+ | |Interact with the world in a way that makes the physics engine do what the attacker wants. | ||
+ | |- | ||
+ | |'''Malform Network Traffic''' | ||
+ | |Send modified network traffic that tricks or disrupts an opposing player or the game itself. | ||
+ | |- | ||
+ | |} | ||
+ | |||
+ | {{Social Media Links}} | ||
+ | |||
+ | | valign="top" style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right:25px;" | | ||
+ | |||
+ | == The Exploits Project == | ||
+ | |||
+ | The Exploits provides information on what types of tools and techniques an attacker might use to accomplish his/her goal. | ||
+ | |||
+ | == Sub-project Leader == | ||
+ | |||
+ | * Daniel Miessler | ||
== Related Projects == | == Related Projects == | ||
Line 251: | Line 316: | ||
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | {| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | ||
− | | valign="top" | + | | valign="top" style="border-right: 1px dotted gray;padding-right:25px;" | |
− | == | + | == Attacker Goals == |
− | + | This list refers to what a given attacker might be trying to accomplish within the game by performing a given attack. This could relate very closely (or not) with the technical impact or business impact cause by the behavior. | |
− | {| | + | {| class="wikitable" border="1" style="text-align: left" |
− | ! | + | ! Attacker Goal |
! Description | ! Description | ||
|- | |- | ||
− | | ''' | + | | '''Avoid Damage''' |
− | | | + | |Allows the player to avoid being killed by other players or NPCs. |
− | |||
− | |||
|- | |- | ||
− | | ''' | + | | '''Gain Gear''' |
− | | | + | |Improve the amount or quality of gear the player has. |
− | |||
− | |||
− | |||
|- | |- | ||
− | | ''' | + | | '''Gain In-game Currency''' |
− | | | + | |Gain more currency than would normally be allowed. |
− | |||
− | |||
|- | |- | ||
− | | ''' | + | | '''Enhance Gear''' |
− | | | + | |Give weapons or other gear powers that they wouldn't normally have. |
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
− | | ''' | + | | '''Take Opponent Offline''' |
− | | | + | |Take a player out of the game so that the attacker's position is improved. |
− | + | |- | |
− | + | |'''Skip Content''' | |
− | + | |Allows player to skip content resuting in a faster completion or objective time | |
− | |||
|- | |- | ||
|} | |} | ||
− | |||
{{Social Media Links}} | {{Social Media Links}} | ||
− | | valign="top" | + | | valign="top" style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right:25px;" | |
− | == What is the | + | == What is the Attacker Goals Project == |
− | The | + | The Attacker Goals Project provides information on what types of outcomes attackers might try to achieve within or outside of the game they're attacking. |
− | == | + | == Sub-project Leader == |
* Daniel Miessler | * Daniel Miessler | ||
Line 327: | Line 379: | ||
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | {| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | ||
− | | valign="top" | + | | valign="top" style="border-right: 1px dotted gray;padding-right:25px;" | |
− | == | + | == Negative Outcomes == |
− | The following is a list of | + | The following is a list of possible negative outcomes that can occur as the result of someone successfully attacking a given game. |
− | {| | + | {| class="wikitable" border="1" style="text-align: left" |
− | ! | + | ! Outcomes |
! Description | ! Description | ||
|- | |- | ||
− | | ''' | + | | '''Currency Magnification''' |
− | | | + | |A player ends up with more currency than they were supposed to have. |
− | |||
− | |||
|- | |- | ||
− | | ''' | + | | '''Player Anger''' |
− | | | + | |Players become extremely agitated by one or more bugs. |
− | |||
− | |||
− | |||
|- | |- | ||
− | | '''Game | + | | '''Players Stop Playing the Game''' |
− | | | + | |Players become so frustrated with the bugs and exploits that they stop playing and/or paying for the game. |
− | |||
− | |||
|- | |- | ||
− | | ''' | + | | '''Invulnerable Positions''' |
− | | | + | |Locations on the map make bases or players unassailable and therefore invulnerable. |
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
− | | ''' | + | | '''Item Multiplication''' |
− | | | + | |Items are duplicated, multiplied, or otherwise increased in an unintended way. |
− | + | |- | |
− | + | |'''Unfair Ladder Victory''' | |
− | + | |A victory is scored in favor of a player or team when they should not have won. | |
− | + | |- | |
+ | |'''Unauthorized Admin Command Use''' | ||
+ | |Regular users are somehow able to execute administrative commands. | ||
|- | |- | ||
+ | |'''Lost Revenue''' | ||
+ | |The game company loses revenue due to bugs, hacks, and player anger. | ||
|} | |} | ||
− | |||
{{Social Media Links}} | {{Social Media Links}} | ||
− | | valign="top" | + | | valign="top" style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right:25px;" | |
− | == What is the | + | == What is the Negative Outcomes Project? == |
− | The | + | The Negative Outcomes Project provides information on what types of situations could manifest within the game if bugs or exploits are not successfully addressed. |
− | == Project | + | == Project Leader == |
* Daniel Miessler | * Daniel Miessler | ||
Line 403: | Line 447: | ||
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | {| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | ||
− | | valign="top" | + | | valign="top" style="border-right: 1px dotted gray;padding-right:25px;" | |
− | |||
− | |||
− | |||
− | |||
+ | == Defenses == | ||
+ | These are some of the common defenses that can be used to counter attacks against various components of a game. | ||
+ | {| class="wikitable" border="1" style="text-align: left" | ||
+ | ! Outcomes | ||
+ | ! Description | ||
+ | |- | ||
+ | | '''Cryptographic Validation of Client''' | ||
+ | |Ensure that the client will not run if it has been modified. | ||
+ | |- | ||
+ | | '''Enterprise-level DDoS Protection''' | ||
+ | |Implement protection against low to mid-tier DDoS attacks against the core gaming infrastructure. | ||
+ | |- | ||
+ | | '''Basic Application Security Defenses''' | ||
+ | |Code-based protections against common application security flaws, such as SQLi, XSS, CSRF, LFI/RFI, etc. | ||
+ | |- | ||
+ | |'''Authentication Lockouts''' | ||
+ | |Lock out a user's account after a certain number of failed attempts. | ||
+ | |- | ||
+ | |'''Two-factor Authentication''' | ||
+ | |Require use of 2FA on a given player's account. | ||
+ | |- | ||
+ | |'''Better Code''' | ||
+ | |Any fixes that can be done in code that aren't covered by other defenses. Could include net code, physics engine, logic fixes, etc. | ||
+ | |- | ||
+ | |'''Server-side Validation''' | ||
+ | |Ensure that validations are performed on the server and not (only) the client. | ||
+ | |} | ||
− | |||
{{Social Media Links}} | {{Social Media Links}} | ||
− | | valign="top" | + | | valign="top" style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right:25px;" | |
== What is the Game Security Vulnerabilities Project? == | == What is the Game Security Vulnerabilities Project? == | ||
Line 442: | Line 508: | ||
== Real-world Examples of Gaming Vulnerabilities== | == Real-world Examples of Gaming Vulnerabilities== | ||
− | ''Vulnerability | + | ''Vulnerability'' |
{| class="wikitable" | {| class="wikitable" | ||
+ | !ID | ||
! style="font-weight: bold;" | Vulnerabilty Name | ! style="font-weight: bold;" | Vulnerabilty Name | ||
! style="font-weight: bold;" | Description | ! style="font-weight: bold;" | Description | ||
! style="font-weight: bold;" | Surface Area | ! style="font-weight: bold;" | Surface Area | ||
− | ! style="font-weight: bold;" | | + | ! style="font-weight: bold;" | Goal |
− | ! style="font-weight: bold;" | | + | ! style="font-weight: bold;" | Techical Impact |
− | ! | + | !Business Impact |
! style="font-weight: bold;" | Defense | ! style="font-weight: bold;" | Defense | ||
! Ref | ! Ref | ||
+ | !Game | ||
! Genre | ! Genre | ||
|- | |- | ||
+ | |V1 | ||
| Local Resource Modification, Client-side Logic Flaw | | Local Resource Modification, Client-side Logic Flaw | ||
| In 2015 The Division experienced an exploit that allowed an attacker to switch weapons rapidly, applying weapon buffs in a stacking manner, with no cap. | | In 2015 The Division experienced an exploit that allowed an attacker to switch weapons rapidly, applying weapon buffs in a stacking manner, with no cap. | ||
| Game Client | | Game Client | ||
| Unfair Player Advantage | | Unfair Player Advantage | ||
− | | Player Anger, Lost Revenue | + | | Player Anger |
− | + | |Players leave, Lost Revenue | |
| Cryptographic Integrity Checks on Game Client | | Cryptographic Integrity Checks on Game Client | ||
| http://www.gamesradar.com/theres-a-division-damage-stacking-glitch-if-youve-got-fast-fingers/ | | http://www.gamesradar.com/theres-a-division-damage-stacking-glitch-if-youve-got-fast-fingers/ | ||
+ | | | ||
| 3PS/1PS/MMO | | 3PS/1PS/MMO | ||
|- | |- | ||
− | | colspan=" | + | |VN1 |
+ | | colspan="10" style="text-align: center;" | "The attacker attacked and edited the <code>LOCAL GAME CLIENT (Attack Surface)</code>, which had a <code>LACK OF CLIENT INTEGRITY CONTROLS (Vulnerability)</code>, which allowed her to <code>ARTIFICIALLY INCREASE HER ABILITIES (Attacker Goal)</code>, ultimately leading to an <code>UNHAPPY PLAYER BASE (Negative Outcome)</code> and <code>DECLINING GAME REVENUE (Negative Outcome)</code> due to cheating, which could have been prevented by <code>CRYPTOGRAPHIC INTEGRITY CHECKS ON GAME CLIENT</code>” | ||
+ | |- | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | |- | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | |- | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | | | ||
|- | |- | ||
+ | | | ||
| | | | ||
| | | | ||
Line 472: | Line 580: | ||
| | | | ||
| | | | ||
+ | | | ||
| | | | ||
| | | | ||
− | | | + | | |
| | | | ||
|} | |} | ||
− | '' | + | ''Working Data Collection Spreadsheet:'' |
− | : | + | https://docs.google.com/spreadsheets/d/1Og08wyHsqtODBDkU_M2zHAvdxc63GSu-OmT8NjCc9Ak/edit#gid=0 |
+ | |||
+ | : | ||
− | |||
{{Social Media Links}} | {{Social Media Links}} | ||
Line 487: | Line 597: | ||
= Community = | = Community = | ||
− | + | We are actively looking for people to help in the following areas: | |
− | + | * Improving the framework schema, e.g., vulns, attack surfaces, technical impacts, business impacts, defenses, etc. | |
− | + | * Adding content to any of the various sections | |
− | + | * Input from avid gamers on how useful this is to them | |
− | + | * Input from app security experts | |
− | + | * Input from security types working at gaming companies | |
− | + | * Input from game company business types | |
− | + | If you have interest in helping, reach out to us and we'll make you a contributor. | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | * | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | * | ||
− | * | ||
− | * | ||
− | * | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
= Testing Tools = | = Testing Tools = | ||
Line 558: | Line 610: | ||
== Commonly Used Game Hacking Tools == | == Commonly Used Game Hacking Tools == | ||
− | |||
{{Social Media Links}} | {{Social Media Links}} | ||
Line 583: | Line 634: | ||
| links_url1 = | | links_url1 = | ||
| links_name1 = | | links_name1 = | ||
− | |||
− | |||
}} | }} | ||
+ | __NOTOC__ <headertabs></headertabs> | ||
− | + | [[Category:OWASP_Project]] | |
− | + | [[Category:OWASP_Document]] | |
− | + | [[Category:OWASP_Download]] | |
− | + | [[Category:OWASP_Release_Quality_Document]] | |
− | |||
− | [[Category:OWASP_Project]] [[Category:OWASP_Document]] [[Category:OWASP_Download]] [[Category:OWASP_Release_Quality_Document]] |
Latest revision as of 17:46, 23 March 2017
- About the Project
- Attack Surfaces
- Vulnerabilities
- Exploits
- Attacker Goals
- Negative Outcomes
- Defenses
- Examples
- Community
- Testing Tools
- Project About
OWASP Game Security Framework (GSF)The OWASP Game Security Framework (GSF) represents a modular approach to understanding the security issues that surround video game ecosystems. In 2016 the videogame market became 99.6 Billion dollar industry... any why shouldn't it be? Some of the most prolific and complex software developed today are video games. They are professionally played, sponsored, scrutinized, monetized, and celebrated, just like many sports. They handle clients, servers, web components, monetary transfers, social interactions, virtual markets, etc, with every bit the need of security that most internet hosted apps have (if not more in some cases). The GSF is designed to help threat model gaming issues that have devastated new games. Most importantly we hope the GSF can help new developers and security testers alike root out bugs in your favorite titles. The framework is broken into three main concepts / sections:
LicensingThe OWASP Game Security Framework is free to use. It is licensed under the http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.
|
What is the OWASP Game Security Framework?The goal of the OWASP Game Security Framework is to provide a structure for discussing the various aspects around the security of video games. The target audience for the project includes:
Project Leaders
Contributors
Related Projects |
CollaborationQuick DownloadCOMING SOON News and Events
Classifications |
Attack SurfacesThe following is a list of the attack surfaces that can be found in video games of various types.
|
What is the Attack Surfaces Section?This section provides an overview of the various places an attacker can target to harm a given game infrastructure. Sub-project Leader
Related ProjectsCollaborationQuick Download
News and Events
|
Game Security VulnerabilitiesThe following is a list of the vulnerabilities that can be found in video games of various types, and the attack surfaces they're likely to be associated with.
|
What is the Game Security Vulnerabilities Project?The Security Vulnerabilities Project provides information on what types of vulnerabilities exist within games, and which attack surfaces they fall under. Sub-project Leader
Related ProjectsCollaborationResourcesNews and Events
|
ExploitsThis list refers to what a given attacker might use to take advantage of a given bug within the game.
|
The Exploits ProjectThe Exploits provides information on what types of tools and techniques an attacker might use to accomplish his/her goal. Sub-project Leader
Related ProjectsCollaborationResourcesNews and Events
|
Attacker GoalsThis list refers to what a given attacker might be trying to accomplish within the game by performing a given attack. This could relate very closely (or not) with the technical impact or business impact cause by the behavior.
|
What is the Attacker Goals ProjectThe Attacker Goals Project provides information on what types of outcomes attackers might try to achieve within or outside of the game they're attacking. Sub-project Leader
Related ProjectsCollaborationResourcesNews and Events
|
Negative OutcomesThe following is a list of possible negative outcomes that can occur as the result of someone successfully attacking a given game.
|
What is the Negative Outcomes Project?The Negative Outcomes Project provides information on what types of situations could manifest within the game if bugs or exploits are not successfully addressed. Project Leader
Related ProjectsCollaborationResourcesNews and Events
|
DefensesThese are some of the common defenses that can be used to counter attacks against various components of a game.
|
What is the Game Security Vulnerabilities Project?The Security Vulnerabilities Project provides information on what types of vulnerabilities exist within games, and which attack surfaces they fall under. Project Leaders
Related ProjectsCollaborationResourcesNews and Events
|
Real-world Examples of Gaming Vulnerabilities
Vulnerability
ID | Vulnerabilty Name | Description | Surface Area | Goal | Techical Impact | Business Impact | Defense | Ref | Game | Genre |
---|---|---|---|---|---|---|---|---|---|---|
V1 | Local Resource Modification, Client-side Logic Flaw | In 2015 The Division experienced an exploit that allowed an attacker to switch weapons rapidly, applying weapon buffs in a stacking manner, with no cap. | Game Client | Unfair Player Advantage | Player Anger | Players leave, Lost Revenue | Cryptographic Integrity Checks on Game Client | http://www.gamesradar.com/theres-a-division-damage-stacking-glitch-if-youve-got-fast-fingers/ | 3PS/1PS/MMO | |
VN1 | "The attacker attacked and edited the LOCAL GAME CLIENT (Attack Surface) , which had a LACK OF CLIENT INTEGRITY CONTROLS (Vulnerability) , which allowed her to ARTIFICIALLY INCREASE HER ABILITIES (Attacker Goal) , ultimately leading to an UNHAPPY PLAYER BASE (Negative Outcome) and DECLINING GAME REVENUE (Negative Outcome) due to cheating, which could have been prevented by CRYPTOGRAPHIC INTEGRITY CHECKS ON GAME CLIENT ”
| |||||||||
Working Data Collection Spreadsheet:
https://docs.google.com/spreadsheets/d/1Og08wyHsqtODBDkU_M2zHAvdxc63GSu-OmT8NjCc9Ak/edit#gid=0
We are actively looking for people to help in the following areas:
- Improving the framework schema, e.g., vulns, attack surfaces, technical impacts, business impacts, defenses, etc.
- Adding content to any of the various sections
- Input from avid gamers on how useful this is to them
- Input from app security experts
- Input from security types working at gaming companies
- Input from game company business types
If you have interest in helping, reach out to us and we'll make you a contributor.
Commonly Used Game Hacking Tools
PROJECT INFO What does this OWASP project offer you? |
RELEASE(S) INFO What releases are available for this project? | |||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|