Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Attacks/Breaches

Dept. Of Energy Breach: Bigger Than We Realized

DOE says July data breach affected more than double the number of people in initial estimates. CIO tasks an independent investigator to probe breach and agency's technology infrastructure.

5 Army Tech Innovations To Watch
5 Army Tech Innovations To Watch
(click image for larger view)
The Department of Energy has revised its count of the number of people whose information was compromised in a July 2013 intrusion that resulted in the theft of personal information.

"The department has now identified approximately 104,179 past and current federal employees, including dependents and contractors, whose name, social security number, and date of birth were compromised by this cyber incident," says a July 2013 Cyber Incident FAQ released by the agency's Office of the CIO.

That data breach victim count more than doubles the number of records that the agency previously thought might have been compromised. Of the people affected, "64,480 are personnel within our direct DOE Federal and M&O [management and operating] Contractor Community, including spouses, dependents, and former employees," according to a memo distributed to DOE employees on Oct. 11, 2013. "The remainder are personnel from other federal agencies and support contractors."

[ Did lax security make DOE vulnerable? Read Energy Dept. Breach: Let's Get Back To Basics. ]

The memo further disclosed that 2,800 employees who have their DOE salary directly deposited into their bank account had that bank account number compromised as well. The agency said it's been able to notify most -- but not all -- of those affected people, owing to the agency not having up-to-date address information on hand for some former employees.

The Oct. 11 memo was written by the DOE's chief of staff, Kevin Knobloch, who joined the agency in June after serving as president of the Union of Concerned Scientists. A copy of the memo was provided anonymously to InformationWeek, and a DOE official confirmed its authenticity.

The July data breach involved DOEInfo, which is an employee database owned and maintained by the agency's Office of the Chief Financial Officer. Sources have told InformationWeek that DOEInfo is an outdated, publicly accessible ColdFusion system that hadn't been patched against known vulnerabilities, and was thus easy pickings for hackers.

DOE employees first learned of the DOEInfo data breach on Aug. 14, when the agency emailed a memo saying that at least 14,000 people had their information compromised as a result. But it warned that the number could change, because the investigation was ongoing, and in an Aug. 29 memo, the agency revised to 53,000 the estimated count of people affected.

With the Oct. 11 memo, however the DOE's big-picture message to agency employees and contractors -- worried about whether their personally identifiable information (PII) might have been compromised -- is that no news equals good news. "If you do not receive a notification letter by October 15, 2013, you should assume it is unlikely your PII was affected," according to the DOE FAQ. "If DOE later determines your PII was affected you will be notified, regardless of the date of discovery."

One piece of good news is that -- based on the ongoing investigation -- attackers don't appear to have been gunning for top-secret project plans or the identity of the agency's nuclear scientists. "Based on the findings of the Department's ongoing investigation into this incident, we do believe PII theft may have been the primary purpose of the attack," says the DOE FAQ. "Accordingly, the Department encourages each affected individual to be extra vigilant and to carefully monitor bank statements, credit card statements, emails and phone calls relating to recent financial transactions."

The DOE said that people affected by the breach will receive an activation code for a free year's worth of monitoring at a designated credit monitoring service. The agency also said that for affected dependents, it has purchased "a family care and protection plan that will monitor the social security numbers for children and youth who do not yet have a credit history." Affected employees will also receive up to four hours of paid time off for dealing with related identity theft prevention and cleanup.

The internal memo said that a related investigation remains ongoing -- meaning that the count of people affected by the breach may yet increase -- and referenced parallel law enforcement efforts. "We are working with interagency partners on actions that can be taken against those responsible and to reduce the likelihood of another successful attack," says Knobloch's memo.

He added that the agency has now also launched a large-scale internal investigation into the attack. "CIO Bob Brese requested in August that the DOE Inspector General conduct a management review of the facts leading up to the attack and compromise of the MIS [management information system] application and the applications and databases to which it connects," says the memo. "That review is underway."

A DOE Inspector General spokeswoman wasn't immediately available to answer questions, such as what constitutes a "management review," or what might result from such an investigation.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Mobile Banking Malware Up 50% in First Half of 2019
Kelly Sheridan, Staff Editor, Dark Reading,  1/17/2020
Active Directory Needs an Update: Here's Why
Raz Rafaeli, CEO and Co-Founder at Secret Double Octopus,  1/16/2020
New Attack Campaigns Suggest Emotet Threat Is Far From Over
Jai Vijayan, Contributing Writer,  1/16/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: I've never actually seen the corporate ladder before.
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
How Enterprises are Attacking the Cybersecurity Problem
How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-5216
PUBLISHED: 2020-01-23
In Secure Headers (RubyGem secure_headers), a directive injection vulnerability is present in versions before 3.9.0, 5.2.0, and 6.3.0. If user-supplied input was passed into append/override_content_security_policy_directives, a newline could be injected leading to limited header injection. Upon seei...
CVE-2020-5217
PUBLISHED: 2020-01-23
In Secure Headers (RubyGem secure_headers), a directive injection vulnerability is present in versions before 3.8.0, 5.1.0, and 6.2.0. If user-supplied input was passed into append/override_content_security_policy_directives, a semicolon could be injected leading to directive injection. This could b...
CVE-2020-5223
PUBLISHED: 2020-01-23
In PrivateBin versions 1.2.0 before 1.2.2, and 1.3.0 before 1.3.2, a persistent XSS attack is possible. Under certain conditions, a user provided attachment file name can inject HTML leading to a persistent Cross-site scripting (XSS) vulnerability. The vulnerability has been fixed in PrivateBin v1.3...
CVE-2019-20399
PUBLISHED: 2020-01-23
A timing vulnerability in the Scalar::check_overflow function in Parity libsecp256k1-rs before 0.3.1 potentially allows an attacker to leak information via a side-channel attack.
CVE-2020-7915
PUBLISHED: 2020-01-22
An issue was discovered on Eaton 5P 850 devices. The Ubicacion SAI field allows XSS attacks by an administrator.