Risk
10/31/2008
04:25 PM
Connect Directly
Google+
LinkedIn
Twitter
RSS
E-Mail
50%
50%

Defense Intelligence Agency Fixes Risky Web Site Code

The presence of a call to execute JavaScript code that resides on a Statcounter.com server in Ireland provided a weak link in the security chain that could have been exploited.

The Defense Intelligence Agency Web site, until earlier this week, exposed job applicants to potential privacy and security risks because it included a link to JavaScript code hosted on a third-party Web site.

While there's no evidence that the site leaked personal information, the presence of a call to execute JavaScript code that resides on a Statcounter.com server in Ireland provided a weak link in the security chain that could have been exploited to provide potentially valuable foreign intelligence about future DIA personnel.

Security researcher Bipin Gautam sent an e-mail to the Full Disclosure security mailing list earlier this week outlining his concerns.

In a follow-up e-mail to InformationWeek, he explained the issue. "If a Web site includes third-party JavaScript like stat counters, advertisement scripts, [or] banners called from third-party servers, the Web site is at risk of having to rely on the third party as well for overall security assurance of its Web site," he said.

In an e-mail, Robert "RSnake" Hansen, CEO of SecTheory and contributor to TechWeb security site Dark Reading, confirmed that the DIA Web site was unnecessarily vulnerable.

"It definitely is an issue if the Web site StatCounter.com were ever to get under an attacker's control," he said. "The site itself is not HTTPS, so it's already vulnerable to man-in-the-middle attacks."

The presence of that third-party JavaScript call, said Hansen, "could give an attacker complete cross-domain read/write into dia.mil."

The DIA was made aware of the risk following Gautam's initial post.

"This code was brought to DIA's attention by individuals within the agency on Monday," said a DIA spokesperson via e-mail. "Upon further investigation, it was resident only on the one page and was determined to be superfluous coding from a previous page incarnation. The code was deleted and no longer resides on DIA servers."

In response to the suggestion by one participant on the Full Disclosure mailing list that the cookie files used by StatCounter.com might have violated federal guidelines, the DIA spokesperson said that the DIA used session cookies (not persistent cookies) for its employment pages only and that the rest of dia.mil is cookie-free.

The spokesperson said, "DIA has followed and continues to follow Department of Defense policy on cookie usage."

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Tech Digest, Dec. 19, 2014
Software-defined networking can be a net plus for security. The key: Work with the network team to implement gradually, test as you go, and take the opportunity to overhaul your security strategy.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-8148
Published: 2015-01-26
The default D-Bus access control rule in Midgard2 10.05.7.1 allows local users to send arbitrary method calls or signals to any process on the system bus and possibly execute arbitrary code with root privileges.

CVE-2014-8157
Published: 2015-01-26
Off-by-one error in the jpc_dec_process_sot function in JasPer 1.900.1 and earlier allows remote attackers to cause a denial of service (crash) or possibly execute arbitrary code via a crafted JPEG 2000 image, which triggers a heap-based buffer overflow.

CVE-2014-8158
Published: 2015-01-26
Multiple stack-based buffer overflows in jpc_qmfb.c in JasPer 1.900.1 and earlier allow remote attackers to cause a denial of service (crash) or possibly execute arbitrary code via a crafted JPEG 2000 image.

CVE-2014-9571
Published: 2015-01-26
Cross-site scripting (XSS) vulnerability in admin/install.php in MantisBT before 1.2.19 and 1.3.x before 1.3.0-beta.2 allows remote attackers to inject arbitrary web script or HTML via the (1) admin_username or (2) admin_password parameter.

CVE-2014-9572
Published: 2015-01-26
MantisBT before 1.2.19 and 1.3.x before 1.3.0-beta.2 does not properly restrict access to /*/install.php, which allows remote attackers to obtain database credentials via the install parameter with the value 4.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
If you’re a security professional, you’ve probably been asked many questions about the December attack on Sony. On Jan. 21 at 1pm eastern, you can join a special, one-hour Dark Reading Radio discussion devoted to the Sony hack and the issues that may arise from it.