{"id":364,"date":"2009-01-08T20:12:16","date_gmt":"2009-01-09T04:12:16","guid":{"rendered":"http:\/\/cubist.cs.washington.edu\/Security\/?p=364"},"modified":"2009-01-09T16:40:35","modified_gmt":"2009-01-10T00:40:35","slug":"current-events-undocumented-chip-in-wii","status":"publish","type":"post","link":"https:\/\/secblog.cs.washington.edu\/Security\/2009\/01\/08\/current-events-undocumented-chip-in-wii\/","title":{"rendered":"Current Events &#8211; Undocumented Chip in Wii"},"content":{"rendered":"<p>&#8220;Update.\u00a0 This entry was updated on &lt;January 9, 2009&gt; to reflect a &lt;re-interpretation of the original article&gt;.<\/p>\n<p>After several years that Wii have been launch, hackers found flaws in Wii\u2019s security aspect. According to an article from Nintendo World Report, a tiny processor that was kept as a secret for security reason is discovered by a group of hackers, Team Twiizers. Because the existence of the chip has been discovered, this can cause security problems.<\/p>\n<p>As presented in this video, in order to run the game on Wii, a ticket (key) is needed. The valid keys are all stored in the chip. However, this chip does not only consist of keys, but also controls the turn on bit of the functionality of DVD playback that is turned off by default. These aspects make the hackers feel challenge to break Nintendo\u2019s security system.<\/p>\n<p><!--more--><\/p>\n<p>One solution that the company can conduct is to decrease the price of software so the hackers will not have motivation to break the system and run illegal copies of the software. Another possible solution is to replace the chip by the one with more capacity so the chip can have a security management.<\/p>\n<p>Once a hacker can break through the security system, he can post his open source-code. The users can download the code, execute it, and run it in Wii. By doing this, Wii\u2019s users will be able to do piracy. On the other hand, since users will have to go online to download software updates or compete with other users, the hacker may have connection to the user\u2019s console. This way, the hacker can get the users\u2019 private data, such as their pictures or game history.<\/p>\n<p>With this security problem, the consumers will want the company to make the code in the chip become open source. The customer can download the code to enable DVD playback. In the other hand, the consumers also have to help companies, not only Wii\u2019s company, to prevent piracy.<\/p>\n<p>&lt; END &gt;<\/p>\n<p><!--more-->&lt;Original&gt;<\/p>\n<p>After several years that Wii have been launch, hackers found flaws in Wii\u2019s security aspect. According to an article from Nintendo World Report, a tiny unlicensed processor was discovered in Wii. This illegally planted chip could be a big problem in the user\u2019s privacy especially when the user goes online.<\/p>\n<p>Internet is never a secure world. Every time we are connected to the internet, there will always be a risk of getting attack. In order to get online in Wii, we assume the user will have to insert a username and a password. With Wii having this undocumented processor, a black hat hacker, a hacker who breaks to security system and harm it, could hack the Wii system; by getting access to the Wii system, hackers can \u201cplay\u201d with it. The hacker can set the system so that some software cannot be run and even get the user\u2019s private data.<\/p>\n<p>A Joysound Wii karaoke software will be released in Japan and users will have to pay for the song library with timed-subscription. Hackers can go down to the system and change the minutes that they or others use while playing this game. This activity can bring advantages and disadvantages to both Wii users and the company.<\/p>\n<p>Out of all those security problems caused by the illegal processor, there is one good point. As stated, the hacker can set the system and authenticate which software can be played that can stop people to copy the software and play it on many other consoles. This issue can prevent piracy.<\/p>\n<p>One possible solution that the company can do is to remove the undocumented processor and redesign Wii. A Wii owner will want the company to fix these potential security problems. Furthermore, the solutions should be found by the company and back in design time, all Wii\u2019s components should be well-documented.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>&#8220;Update.\u00a0 This entry was updated on &lt;January 9, 2009&gt; to reflect a &lt;re-interpretation of the original article&gt;. After several years that Wii have been launch, hackers found flaws in Wii\u2019s security aspect. According to an article from Nintendo World Report, &hellip; <a href=\"https:\/\/secblog.cs.washington.edu\/Security\/2009\/01\/08\/current-events-undocumented-chip-in-wii\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":80,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,13,9],"tags":[],"class_list":["post-364","post","type-post","status-publish","format-standard","hentry","category-current-events","category-physicalsecurity","category-privacy"],"_links":{"self":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts\/364","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/users\/80"}],"replies":[{"embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/comments?post=364"}],"version-history":[{"count":22,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts\/364\/revisions"}],"predecessor-version":[{"id":393,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts\/364\/revisions\/393"}],"wp:attachment":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/media?parent=364"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/categories?post=364"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/tags?post=364"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}