Sony BMG copy protection rootkit scandal

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Sony BMG XCP audio CD player

A scandal erupted in 2005 regarding Sony BMG's implementation of deceptive, illegal, and potentially harmful copy protection measures on about 22 million CDs. When inserted into a computer, the CDs installed one of two pieces of software which provided a form of digital rights management (DRM) by modifying the operating system to interfere with CD copying. Neither program could easily be uninstalled, and they created vulnerabilities that were exploited by unrelated malware. Sony claims this was unintentional. One of the programs installed even if the user refused its EULA, and it "phoned home" with reports on the user's private listening habits; the other was not mentioned in the EULA at all, contained code from several pieces of open-source software in an apparent infringement of copyright, and configured the operating system to hide the software's existence, leading to both programs being classified as rootkits.

Sony BMG initially denied that the rootkits were harmful. It then released, for one of the programs, an "uninstaller" that only un-hid the program, installed additional software which could not be easily removed, collected an email address from the user, and introduced further security vulnerabilities.

Following public outcry, government investigations, and class-action lawsuits in 2005 and 2006, Sony BMG partially addressed the scandal with consumer settlements, a recall of about 10% of the affected CDs, and the suspension of CD copy protection efforts in early 2007.

Background

In August 2000, statements by Sony Pictures Entertainment US senior VP Steve Heckler foreshadowed the events of late 2005. Heckler told attendees at the Americas Conference on Information Systems "The industry will take whatever steps it needs to protect itself and protect its revenue streams... It will not lose that revenue stream, no matter what... Sony is going to take aggressive steps to stop this. We will develop technology that transcends the individual user. We will firewall Napster at source - we will block it at your cable company. We will block it at your phone company. We will block it at your ISP. We will firewall it at your PC... These strategies are being aggressively pursued because there is simply too much at stake."[1]

In Europe, BMG created a minor scandal in 2001 when it released Natalie Imbruglia's second album, White Lilies Island, without warning labels stating that the CD had copy protection.[2][3] The CDs were eventually replaced.[2][3] BMG and Sony both released copy-protected versions of certain releases in certain markets in late 2001,[4][5] and a late 2002 report indicated that all BMG CDs sold in Europe would have some form of copy protection.[6]

Copy-protection software

The two pieces of copy-protection software at issue in the 2005–2007 scandal were included on over 22 million CDs[7] marketed by Sony BMG, the record company formed by the 2004 merger of Sony and BMG's recorded music divisions. About two million of those CDs,[7] spanning 52 titles, contained First 4 Internet (F4I)'s Extended Copy Protection (XCP), which was installed on Microsoft Windows systems after the user accepted the EULA which made no mention of the software. The remaining 20 million CDs,[7] spanning 50 titles,[8] contained SunnComm's MediaMax CD-3, which was installed on either Microsoft Windows or Mac OS X systems after the user was presented with the EULA, regardless of whether the user accepted it (although Mac OS X prompted the user for confirmation when the software sought to modify the OS).

XCP rootkit

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Extended Copy Protection

The scandal erupted on October 31, 2005, when Winternals (later acquired by Microsoft) researcher Mark Russinovich posted to his blog a detailed description and technical analysis of F4I's XCP software that he ascertained had been recently installed on his computer by a Sony BMG music CD. Russinovich compared the software to a rootkit due to its surreptitious installation and its efforts to hide its existence. He noted that the EULA does not mention the software, and he asserted emphatically that the software is illegitimate and that digital rights management had "gone too far".[9]

Anti-virus firm F-Secure concurred, "Although the software isn't directly malicious, the used rootkit hiding techniques are exactly the same used by malicious software to hide themselves. The DRM software will cause many similar false alarms with all AV software that detect rootkits. ... Thus it is very inappropriate for commercial software to use these techniques."[10] After public pressure, Symantec[11] and other anti-virus vendors included detection for the rootkit in their products as well, and Microsoft announced it would include detection and removal capabilities in its security patches.[12]

Russinovich discovered numerous problems with XCP:

  • It creates security holes that can be exploited by malicious software such as worms or viruses.
  • It constantly runs in the background and excessively consumes system resources, slowing down the user's computer, regardless of whether there is a protected CD playing.
  • It employs unsafe procedures to start and stop, which could lead to system crashes.
  • It has no uninstaller, and is installed in such a way that inexpert attempts to uninstall it can lead to the operating system to fail to recognize existing drives.

Soon after Russinovich's first post, there were several trojans and worms exploiting XCP's security holes. Some people even used the vulnerabilities to cheat in online games.[13]

Sony BMG quickly released software to remove the rootkit component of XCP from affected Microsoft Windows computers,[14] but after Russinovich analyzed the utility, he reported in his blog that it only exacerbated the security problems and raised further concerns about privacy.[15] Russinovich noted that the removal program merely unmasked the hidden files installed by the rootkit, but did not actually remove the rootkit. He also reported that it installed additional software that could not be uninstalled. In order to download the uninstaller, he found it was necessary to provide an e-mail address (which the Sony BMG Privacy Policy implied was added to various bulk e-mail lists), and to install an ActiveX control containing backdoor methods (marked as "safe for scripting", and thus prone to exploits).[16][17]

On November 18, 2005, Sony BMG provided a "new and improved" removal tool to remove the rootkit component of XCP from affected Microsoft Windows computers.

MediaMax CD-3

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: MediaMax CD-3

Lua error in package.lua at line 80: module 'strict' not found.

Legal and financial problems

Product recall

On November 15, 2005 vnunet.com announced[18] that Sony BMG was backing out of its copy-protection software, recalling unsold CDs from all stores, and offering consumers to exchange their CDs with versions lacking the software. The Electronic Frontier Foundation compiled a partial list of CDs with XCP.[19] Sony BMG was quoted as maintaining that "there were no security risks associated with the anti-piracy technology", despite numerous virus and malware reports. On November 16, 2005, US-CERT, part of the United States Department of Homeland Security, issued an advisory on XCP DRM. They said that XCP uses rootkit technology to hide certain files from the computer user, and that this technique is a security threat to computer users. They also said one of the uninstallation options provided by Sony BMG introduces further vulnerabilities to a system. US-CERT advised, "Do not install software from sources that you do not expect to contain software, such as an audio CD."[20]

Sony BMG announced that it had instructed retailers to remove any unsold music discs containing the software from their shelves.[21] It was estimated by internet security expert Dan Kaminsky that XCP was in use on more than 500,000 networks.[22]

CDs with XCP technology can be identified by the letters "XCP" printed on the back cover of the jewel case for the CD according to SonyBMG's XCP FAQ.[23]

On November 18, 2005 Reuters reported that Sony BMG would exchange affected insecure CDs for new unprotected disks as well as unprotected MP3 files.[24]

Information about the swap can be found at the Sony BMG swap program website.[25] As a part of the swap program, consumers can mail their XCP-protected CDs to Sony BMG and be sent an unprotected disc via return mail.

On November 29 then New York Attorney General Eliot Spitzer found through his investigators that, despite the recall of November 15, Sony BMG CDs with XCP were still for sale in New York City music retail outlets. Spitzer said "It is unacceptable that more than three weeks after this serious vulnerability was revealed, these same CDs are still on shelves, during the busiest shopping days of the year, [and] I strongly urge all retailers to heed the warnings issued about these products, pull them from distribution immediately, and ship them back to Sony."[26]

The next day, Massachusetts Attorney General Tom Reilly issued a statement saying that Sony BMG CDs with XCP were still available in Boston despite the Sony BMG recall of November 15.[27] Attorney General Reilly advised consumers not to purchase the Sony BMG CDs with XCP and said that he was conducting an investigation of Sony BMG.

As of May 11, 2006 Sony BMG's website offered consumers a link to "Class Action Settlement Information Regarding XCP And MediaMax Content Protection."[28] It has online claim filing and links to software updates/uninstallers. The deadline for submitting a claim was June 30, 2007.

As of April 2, 2008 Sony BMG's website finally offered consumers their explanation and list of affected CDs.[29]

Texas state action

On November 21, 2005, Texas Attorney General Greg Abbott sued Sony BMG.[30] Texas was the first state in the United States to bring legal action against Sony BMG in response to the rootkit. The suit was also the first filed under the state’s 2005 spyware law. It alleged that the company surreptitiously installed the spyware on millions of compact music discs (CDs) that consumers inserted into their computers when they play the CDs, which can compromise the systems.

On December 21, 2005, Abbott added new allegations to his lawsuit against Sony-BMG, regarding MediaMax.[31] The new allegations claimed that MediaMax violated the state's spyware and deceptive trade practices laws, because the MediaMax software would be installed on a computer even if the user declined the license agreement that would authorize its installation. Abbott stated, "We keep discovering additional methods Sony used to deceive Texas consumers who thought they were simply buying music", and "Thousands of Texans are now potential victims of this deceptive game Sony played with consumers for its own purposes." In addition to violations of the Consumer Protection Against Computer Spyware Act of 2005, which allowed for civil penalties of $100,000 for each violation of the law, the alleged violations added in the updated lawsuit (on December 21, 2005) carried maximum penalties of $20,000 per violation.[32][33] Sony lost the battle with Abbott and had to pay $750,000 in legal fees to Texas, accept customer returns of affected CDs, place a conspicuous detailed notice on their homepage and make "keyword buys" to alert consumers by advertising with Google, Yahoo! and MSN, pay up to $150 per damaged computer, and much more. Sony BMG also had to agree that they would not make any claim that the legal settlement in any way constitutes the approval of the court. [34]

New York and California class action suits

Class action suits were filed against Sony BMG in New York and California.[35]

On December 30, 2005, the New York Times reported that Sony BMG has reached a tentative settlement of the lawsuits, proposing two ways of compensating consumers who have purchased the affected recordings.[36] According to the proposed settlement, those who purchased an XCP CD will be paid $7.50 per purchased recording and given the opportunity to download a free album, or be able to download three additional albums from a limited list of recordings if they give up their cash incentive. District Judge Naomi Reice Buchwald entered an order tentatively approving the settlement on January 6, 2006.

The settlement is designed to compensate those whose computers were infected, but not otherwise damaged. Those who have damages that are not addressed in the class action are able to opt out of the settlement and pursue their own litigation.

A fairness hearing was held on May 22, 2006 at 9:15 am at the Daniel Patrick Moynihan United States Courthouse for the Southern District of New York.

Claims had to be submitted by December 31, 2006. Class members who wished to be excluded from the settlement must have filed before May 1, 2006. Those who remained in the settlement could attend the fairness hearing at their own expense and speak on their own behalf or be represented by an attorney.

Other actions

In Italy, ALCEI (an association similar to EFF) also reported the rootkit to the Financial Police, asking for an investigation under various computer crime allegations, along with a technical analysis of the rootkit.[37][38]

The US Department of Justice (DOJ) made no comment on whether it would take any criminal action against Sony. However, Stewart Baker of the Department of Homeland Security publicly admonished Sony, stating, "it's your intellectual property—it's not your computer".[39]

On November 21, the EFF announced that it was also pursuing a lawsuit over both XCP and the SunnComm MediaMax DRM technology. The EFF lawsuit also involves issues concerning the Sony BMG end user license agreement.

It was reported on December 24, 2005 that then-Florida Attorney General Charlie Crist was investigating Sony BMG spyware.[40]

On January 30, 2007, the U.S. Federal Trade Commission (FTC) announced a settlement with Sony BMG on charges that their CD copy protection had violated Federal law[41]—Section 5(a) of the Federal Trade Commission Act, 15 USC 45(a)—by engaging in unfair and deceptive business practices.[42] The settlement requires Sony BMG to reimburse consumers up to $150 to repair damage that resulted directly from their attempts to remove the software installed without their consent.[41] The settlement also requires them to provide clear and prominent disclosure on the packaging of future CDs of any limits on copying or restrictions on the use of playback devices, and ban the company from installing content protection software without obtaining consumers’ authorization.[41] FTC chairwoman Deborah Platt Majoras added that, "Installations of secret software that create security risks are intrusive and unlawful. Consumers' computers belong to them, and companies must adequately disclose unexpected limitations on the customer use of their products so consumers can make informed decisions regarding whether to purchase and install that content."[43][44]

Copyright infringement

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Extended Copy Protection § Copyright violations

Researchers found that Sony BMG and the makers of XCP also apparently infringed copyright by failing to adhere to the licensing requirements of various pieces of open-source software whose code was used in the program,[45][46] including the LAME MP3 encoder,[47] mpglib,[48] FAAC,[49] id3lib,[50] mpg123 and the VLC media player.[51]

In January 2006, the developers of LAME posted an open letter stating that they expected "appropriate action" by Sony BMG, but that the developers had no plans to investigate or take action over the apparent violation of LAME's source code license.[52]

Company and press reports

Russinovich's report was being discussed on popular blogs almost immediately following its release.[53]

NPR was one of the first major news outlets to report on the scandal on November 4, 2005. Thomas Hesse, Sony BMG's Global Digital Business President, told reporter Neda Ulaby, "Most people, I think, don't even know what a rootkit is, so why should they care about it?"[54]

In November 7, 2005 article, vnunet.com summarised Russinovich's findings,[55] and urged consumers to avoid buying Sony BMG music CDs for the time being. The following day, The Boston Globe classified the software as spyware and Computer Associates' eTrust Security Management unit VP Steve Curry confirmed that it communicates personal information from consumers' computers to Sony BMG (namely the CD being played and the user's IP address).[56] The methods used by the software to avoid detection were likened to those used by data thieves.

On November 8, 2005, Computer Associates decided to classify Sony BMG's software as "spyware" and provide tools for its removal.[57] Speaking about Sony BMG suspending the use of XCP, independent researcher Mark Russinovich said, "This is a step they should have taken immediately."[58]

The first virus which made use of Sony BMG's stealth technology to make malicious files invisible to both the user and anti-virus programs surfaced on November 10, 2005.[59] One day later Yahoo! News announced that Sony BMG had suspended further distribution of the controversial technology.

According to ZDNet News: "The latest risk is from an uninstaller program distributed by SunnComm Technologies, a company that provides copy protection on other Sony BMG releases." The uninstall program obeys commands sent to it allowing others "to take control of PCs where the uninstaller has been used."[60]

On December 6, 2005, Sony BMG said that 5.7 million CDs spanning 27 titles were shipped with MediaMax 5 software. The company announced the availability of a new software patch to prevent a potential security breach in consumers' computers.

Sony BMG in Australia released a press release indicating that no Sony BMG titles manufactured in Australia have copy protection.[61]

See also

Footnotes

  1. ↑ Anastasi, Michael A. "Sony Exec: We Will Beat Napster," New Yorkers For Fair Use web site, August 17, 2000. Retrieved November 13, 2006.
  2. ↑ 2.0 2.1 Lua error in package.lua at line 80: module 'strict' not found. (Archived by WebCite at http://www.webcitation.org/5jG7thyTO)
  3. ↑ 3.0 3.1 Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ 7.0 7.1 7.2 Sony BMG litigation info
  8. ↑ "Anti-Piracy CD Problems Vex Sony", BBC News. Retrieved November 22, 2006.
  9. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ Larvala, Samuli. "F-Secure Rootkit Information : XCP DRM Software", F-secure Computer Rootkit Information Pages, November 29, 2005. Retrieved November 1, 2006. Archived January 14, 2007 at the Wayback Machine
  11. ↑ "SecurityRisk.First4DRM", Symantec Security Response, November 2005. Retrieved November 22, 2006.
  12. ↑ "Sony's DRM Rootkit: The Real Story", Schneier On Security, November 17, 2005. Retrieved November 22, 2006.
  13. ↑ World of Warcraft hackers using Sony BMG rootkit
  14. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ "More on Sony: Dangerous Decloaking Patch, EULAs and Phoning Home", Mark's Blog, November 4, 2005. Retrieved November 22, 2006.
  16. ↑ Nikki, Matti. "Muzzy's research about Sony's XCP DRM system", December 6, 2005. Retrieved June 21, 2014.
  17. ↑ Attack targets Sony 'rootkit' fix
  18. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ "First 4 Internet XCP DRM Vulnerabilities"[dead link], US-CERT Activity Archive, November 15, 2005. Retrieved November 22, 2006.
  21. ↑ Taylor, Paul. "Sony BMG bows to pressure", Financial Times, November 17, 2005. Retrieved November 22, 2006.
  22. ↑ "More pain for Sony over CD code", BBC News, November 17, 2005. Retrieved November 22, 2006.
  23. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  24. ↑ [1][dead link]
  25. ↑ http://cp.sonybmg.com/xcp/
  26. ↑ Hesseldahl, Arik. " Spitzer Gets on Sony BMG's Case ", BusinessWeek Online, November 29, 2005. Retrieved November 22, 2006.
  27. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  28. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  29. ↑ CD’s Containing XCP Content Protection Technology at the Wayback Machine (archived October 12, 2007)
  30. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  31. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  32. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  33. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  34. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  35. ↑ "Sony sued over copy-protected CDs; Sony BMG is facing three lawsuits over its controversial anti-piracy software", BBC News, November 10, 2005. Retrieved November 22, 2006.
  36. ↑ "Sony BMG Tentatively Settles Suits on Spyware", Associated Press report in The New York Times, December 30, 2005, retrieved November 22, 2006. (Free web registration required to view content.)
  37. ↑ "Crist's office joins Sony BMG spyware probe"[dead link], The Inquirer, November 7, 2005. Retrieved November 22, 2006.
  38. ↑ ALCEI Press Release - Legal proceedings in Italy by ALCEI against Sony for a “criminal” offense
  39. ↑ Menta, Richard. Bush Administration to Sony: It's your intellectual property -- it's not your computer. November 12, 2005.
  40. ↑ "Crist's office joins Sony BMG spyware probe", St. Petersburg Times Online, December 24, 2005. Retrieved November 22, 2006.
  41. ↑ 41.0 41.1 41.2 Lua error in package.lua at line 80: module 'strict' not found.
  42. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  43. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  44. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  45. ↑ Proof that F4I violates the GPL - Programming stuff
  46. ↑ Sony's XCP DRM
  47. ↑ Is Sony in violation of the LGPL? - Part II - Programming stuff
  48. ↑ Breakthrough after breakthrough in the F4I case - Programming stuff
  49. ↑ Two new F4I license infringements found - Programming stuff
  50. ↑ http://the-interweb.com/bdump/misc/id3lib.png
  51. ↑ Sam Hocevar’s .plan
  52. ↑ Open letter to Sony BMG (and its owners, Sony and Bertelsmann), First4Internet, and the LAME community.
  53. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  54. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  55. ↑ vnunet.com analysis: Sony CD rootkit could spell doom - vnunet.com[dead link]
  56. ↑ Bray, Hiawatha. "Security firm: Sony CDs secretly install spyware", The Boston Globe, November 8, 2005. Retrieved November 22, 2006.
  57. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  58. ↑ "Microsoft to remove Sony CD code; Sony's controversial anti-piracy CD software has been labelled as spyware by Microsoft.", BBC News, November 14, 2005. Retrieved November 22, 2006.
  59. ↑ Sanders, Tom, and Thompson, Iain. "Virus writers exploit Sony DRM; Sony doomsday scenario becomes reality"[dead link], vnunet.com, 2005-11-10. Retrieved 2006-11-22.
  60. ↑ Halderman, J. Alex "Not Again! Uninstaller for Other Sony DRM Also Opens Huge Security Hole", Freedom to Tinker, November 17, 2005. Retrieved November 22, 2006.
  61. ↑ "No Copy Protection on Australian Sony BMG CDs". Retrieved 18 January 2007.

References

External links

Retrieved from "https://infogalactic.com/w/index.php?title=Sony_BMG_copy_protection_rootkit_scandal&oldid=2158751"