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.

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/14/2020
Omdia Research Launches Page on Dark Reading
Tim Wilson, Editor in Chief, Dark Reading 7/9/2020
Why Cybersecurity's Silence Matters to Black Lives
Tiffany Ricks, CEO, HacWare,  7/8/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-13934
PUBLISHED: 2020-07-14
An h2c direct connection to Apache Tomcat 10.0.0-M1 to 10.0.0-M6, 9.0.0.M5 to 9.0.36 and 8.5.1 to 8.5.56 did not release the HTTP/1.1 processor after the upgrade to HTTP/2. If a sufficient number of such requests were made, an OutOfMemoryException could occur leading to a denial of service.
CVE-2020-13935
PUBLISHED: 2020-07-14
The payload length in a WebSocket frame was not correctly validated in Apache Tomcat 10.0.0-M1 to 10.0.0-M6, 9.0.0.M1 to 9.0.36, 8.5.0 to 8.5.56 and 7.0.27 to 7.0.104. Invalid payload lengths could trigger an infinite loop. Multiple requests with invalid payload lengths could lead to a denial of ser...
CVE-2020-15721
PUBLISHED: 2020-07-14
RosarioSIS through 6.8-beta allows modules/Custom/NotifyParents.php XSS because of the href attributes for AddStudents.php and User.php.
CVE-2020-7592
PUBLISHED: 2020-07-14
A vulnerability has been identified in SIMATIC HMI Basic Panels 1st Generation (incl. SIPLUS variants) (All versions), SIMATIC HMI Basic Panels 2nd Generation (incl. SIPLUS variants) (All versions), SIMATIC HMI Comfort Panels (incl. SIPLUS variants) (All versions), SIMATIC HMI KTP700F Mobile Arctic ...
CVE-2020-7593
PUBLISHED: 2020-07-14
A vulnerability has been identified in LOGO! 8 BM (incl. SIPLUS variants) (V1.81.01 - V1.81.03), LOGO! 8 BM (incl. SIPLUS variants) (V1.82.01), LOGO! 8 BM (incl. SIPLUS variants) (V1.82.02). A buffer overflow vulnerability exists in the Web Server functionality of the device. A remote unauthenticate...