United States: The FTC's Recent Enforcement Action Against Oracle Further Expands The Growing Pool Of Potential Data Security Defendants

On December 21, 2015, Oracle Corporation (“Oracle”) reached an agreement with the Federal Trade Commission (“FTC”) to settle charges that it allegedly deceived customers regarding the security provided by updates to its Java Platform, Standard Edition software (“Java SE”). The proposed consent order requires Oracle to provide information about older versions of Java SE on consumers’ computers and to give consumers the ability to easily uninstall older versions of Java SE. The action is significant because it represents a growing trend in which public and private plaintiffs seek to hold parties responsible for alleged data security failures even though such parties did not themselves collect or receive personal information from consumers. In addition, the case illustrates the FTC’s willingness to seek to hold companies responsible for what some might consider boilerplate statements about the security of their products, even when there is no suggestion that such statements influenced consumers’ purchasing decisions.

I. Overview of the Action

The FTC’s enforcement action against Oracle relates to Java SE, which has been installed on over 850 million personal computers. Java SE provides support for a vast array of features consumers use when browsing the web, including online gaming, chatrooms, and 3D images.

Sun Microsystems first debuted Java SE in the late 1990s. After acquiring Sun in 2010, Oracle has released several new versions of Java SE. According to the FTC, when consumers installed certain updates to Java SE in approximately 2010 or later, they were shown messages stating that “Java provides safe and secure access to . . . Java content” and that consumers would have “the latest . . . security improvements.” Since at least 2010, however, Oracle allegedly was aware of at least 44 types of malware that had been developed. For example, the FTC alleged that attackers used known exploit kits to install key loggers that would capture consumers’ usernames and passwords, which could be used to log into a consumer’s financial accounts. In addition, since at least 2011, Oracle allegedly knew but did not inform consumers (hereinafter, the “incomplete disclosure”) that Java SE updates did not automatically remove all prior versions of Java SE that had been installed on a consumer’s computer.

According to the FTC, Oracle’s alleged incomplete disclosure was a deceptive act that violated Section 5(a) of the Federal Trade Commission Act, 15 U.S.C. § 45(a), and affected consumers in three ways. First, the FTC alleged that consumers were more likely to unknowingly have older, allegedly less secure versions of Java SE installed on their computers. Second, attackers allegedly targeted the vulnerabilities in the older versions of Java SE and obtained consumers’ personal information. Finally, by failing to inform consumers that the Java SE update process did not remove all previously installed versions from consumers’ computers, Oracle allegedly left consumers vulnerable to the foreseeable risk that attackers would target these computers through malware and steal consumers’ personal information.

The FTC and Oracle agreed to a proposed order that requires Oracle to (i) notify existing Java SE users that they may have older, allegedly less secure versions of Java SE on their computer, (ii) provide information to consumers about versions of Java SE that would be installed before and after installing a Java SE update, and how to remove any older versions, and (iii) provide consumers with information and a tool for uninstalling older versions of Java SE. The proposed order also requires that Oracle refrain from misrepresenting (i) the privacy or security of Java SE or similar software, or (ii) how to uninstall older iterations of the software.

II. Expanding the Pool of Defendants

The FTC’s enforcement action against Oracle is notable in several respects. First, the action underscores the recent trend by plaintiffs and regulatory agencies to expand the pool of defendants in data security litigation and regulatory enforcement actions. Traditionally, the FTC and other public and private actors have sought to hold liable companies that collect or use personal information that is the subject of an alleged breach. See e.g., FTC, Protecting Consumer Privacy in an Era of Rapid Change, at 22 (2012), available here (stating that the FTC’s proposed privacy framework applies to “commercial entities that collect or use consumer data”). Recently, data breach plaintiffs and regulatory authorities have sought to expand the boundaries of liability to any party who may have had some role in putting personal information at risk of unauthorized access. The FTC has been one of the primary forces behind this trend, with enforcement actions against TRENDnet, Inc. (manufacturer of web-based cameras), Upromise, Inc. (developer of web-browser toolbar), and this recent action against Oracle, among others, illustrating the FTC’s shift in focus toward product manufacturers and application providers that allegedly expose personal information (broadly construed) to a risk of unauthorized access. See In re TRENDnet, Inc., Complaint, FTC Dkt. No. C-4426 (Jan. 16, 2014); In re Upromise, Inc., Complaint, FTC Dkt. No. C-4351 (Mar. 27, 2012). 

Not to be outdone, state attorneys general and individual and class action plaintiffs have similarly sought to expand the pool of defendants liable for a data breach. For example, a federal court held that Cotton Patch Cafe, Inc.’s claims for violation of Texas’s Deceptive Trade Practices Act, negligent misrepresentation, and fraud by nondisclosure claims could proceed to trial against Micros Systems, Inc. (payment processing equipment provider), where Cotton Patch claimed that the credit card processing system sold by Micros to Cotton Patch did not comply with industry regulations and caused a data breach at a Cotton Patch restaurant. Cotton Patch Cafe, Inc. v. Micros Sys., Inc., CIV.A. MJG-09-03242, 2012 WL 5986773 (D. Md. Nov. 27, 2012). Similarly, in 2015, the Connecticut Attorney General’s Office and class action plaintiffs initiated an investigation and a federal lawsuit, respectively (both of which are still ongoing), against Lenovo Inc. (computer manufacturer) and Superfish (application provider) regarding Superfish software that was pre-installed on Lenovo computers and allegedly put consumers at risk of hacker activity. Press Release, State of Connecticut Office of the Attorney General, AG Jepsen Opens Inquiry into Lenovo, Superfish Privacy and Security Concerns (Mar. 2, 2014), available here; In re: Lenovo Adware Litig., Case No. 5:15-md-02624 (N.D. Cal. 2015) (consolidating approximately 22 cases in a multi-district litigation).

A security compliance assessor also recently was sued in connection with data breaches. Trustwave Holdings Inc., an IT security firm, has been sued in connection with the 2013 data breach of the South Carolina Department of Revenue, for which Trustwave allegedly performed security services, but Trustwave successfully defeated the action at the motion to dismiss stage. Trustwave also was sued twice in connection with its alleged assessments of Target Corporation’s compliance with payment card industry security standards in the years prior to Target’s 2013 data breach, but one suit was voluntarily dismissed and Trustwave was dropped from the other suit when it was consolidated with other suits against Target in the MDL litigation. 

Even a third-party contractor whose work was unrelated to the data security field has been sued when its client suffered a data breach that was allegedly linked to the contractor. In 2015, the Office of Personnel Management (“OPM”) and KeyPoint Government Solutions (“KeyPoint”) were sued in connection with OPM’s 2015 data breach. KeyPoint, which conducts background investigations for the federal government, suffered its own data breach in December 2014 in which KeyPoint’s OPM credentials were allegedly stolen and then used by intruders to gain unauthorized access to OPM’s systems. The case is currently pending.

Overall, governmental and private plaintiffs appear interested in suing any parties with any role affecting the security of a company or individual that suffers a breach. As defendants fight back, courts may be called upon to determine the point at which a party’s role in allegedly putting personal information at risk is too attenuated to warrant liability for a data breach.

III. Statements about Security

The FTC’s enforcement action against Oracle also represents another example of how the FTC continues to aggressively pursue enforcement actions based on statements commonly used in technology product marketing. The FTC’s complaint pointed to two messages about security that customers might view during the Java SE installation process. One message indicated that by utilizing Java’s auto-update process, consumers would have “the latest . . . security improvements.” This statement is not far-reaching – Java SE consumers might not have been able to receive security updates sooner than by using the auto-update feature, and the security improvement may well have been the most recent ones released. The second message merely said that “Java provides safe and secure access to . . . Java content.” 

The FTC based its claims on these statements even though, as the FTC’s complaint acknowledged, in 2010 Oracle had disclosed in a separate FAQ page that consumers could have older versions of Java SE on their computers and that by removing the older versions “Java applications will run with the most up-to-date security.” While the FTC acknowledged this disclosure, the FTC found it inadequate since it was not linked to the allegedly deceptive statements and did not expressly explain that the update process did not automatically remove all older versions of Java SE. 

The FTC’s action against Oracle also further illustrates the FTC’s aggressive interpretation of the “materiality” requirement for a deception claim. Courts have held that a deception claim under Section 5 of the FTC Act requires proof that a representation, omission, or practice was material, meaning that it “involves information that is important to consumers and, hence, likely to affect their choice of, or conduct regarding, a product.” FTC v. Cantkier, 767 F. Supp. 2d 147, 152 (D.D.C. 2011) (quoting F.T.C. v. Cyberspace.Com LLC, 453 F.3d 1196, 1201 (9th Cir. 2006)). In support of this requirement, the FTC alleged only that Oracle’s alleged failure to disclose that all prior versions of Java SE would not be removed during the update process “would be material to consumers’ decisions whether to take further action after ‘updating’ Java SE to protect their computers.” The notion that consumers carefully digest all statements made about data security during the software update process, and then make decisions about “whether to take further action,” is debatable.

By arguing that such statements by Oracle during the Java SE installation process qualified as a deceptive act under the FTC Act – even though the company’s website had already made disclosures regarding potential security issues associated with older versions of the software and the statements were not made in an advertising context – the FTC may ironically discourage some companies from providing information to consumers about their data security practices, out of fear that any perceived incompleteness in the statements will be treated as “deceptive.” The FTC’s decision to proceed in this case underscores that companies should carefully weigh the risks of making statements about data security, particularly when there is no legal or business need to make the statements. Those companies that do decide to make statements about data security should take note of the FTC’s apparent contention in the Oracle matter that caveats needed to make a statement non-deceptive must appear in proximity to the statement. 

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

In association with
Related Video
Up-coming Events Search
Font Size:
Mondaq on Twitter
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
Email Address
Company Name
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement

Mondaq.com (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of www.mondaq.com

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about Mondaq.com’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.


Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.


Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to unsubscribe@mondaq.com with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.


A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.


This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.


If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.


This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to webmaster@mondaq.com.

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to EditorialAdvisor@mondaq.com.

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at enquiries@mondaq.com.

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at problems@mondaq.com and we will use commercially reasonable efforts to determine and correct the problem promptly.