Risk
1/23/2009
05:49 PM
Connect Directly
Google+
LinkedIn
Twitter
RSS
E-Mail
50%
50%

White House Web Site Revisits Privacy Policy

Staffers address privacy concerns after a 1-by-1-pixel image file loaded by Web page code for tracking purposes is revealed.

The script sends more than two dozen system configuration details, including the referring URL that brought the user to the WhiteHouse.gov site; the ID of any WebTrends cookie already installed on the visitor's system; the language the browser is set to; time since last visit; current time; and whether Java, Flash, and Silverlight are installed.

Champeon also observed that if the user's browser has a query box, the WebTrends JavaScript will include any text in the box. At least in Firefox 3, queries typed into the query box are retained. That means a search conducted through one's browser query box prior to visiting the White House site would be transmitted to WebTrends. While searches generally aren't considered to be personal information, they can be, as the AOL search data fiasco in 2006 demonstrated.

Jascha Kaykas-Wolff, VP of marketing at WebTrends, explained that the client determines whether search information is tracked for site analysis purposes and that it's useful data for Web site managers who want to figure out what content site users are looking for.

People differ about whether using JavaScript this way is a security risk. "It's not a particularly safe practice or good for privacy, although most major sites still do it anyway, using WebTrends, Omniture, or Google Analytics," said Robert Hansen, CEO of security consultancy SecTheory, in an e-mail.

"We pay very close attention to [JavaScript issues] because it's very important to us from a privacy and security perspective," said Eric Butler, director of engineering at WebTrends. "This is stuff that has been vetted by security and privacy folks on a continuous basis. We feel pretty confident we're within industry standards." He added that WebTrends has deliberately not obfuscated its code so that people can read it.

Champeon said that the White House should acknowledge what's going on more thoroughly in its privacy policy, but doesn't see a significant problem, with the possible exception of the WebTrends code that is able to access a site visitor's query box.

Auerbach's concern has to do with the government's responsibilities under the Privacy Act. "WebTrends gets to see this [data], to keep it, to aggregate and cross-link it with other data, and to sell it to others, with no visible constraint from the WhiteHouse.gov privacy policy," he said.

WebTrends insists this isn't the case. "Our customers own their data," said Eric Butler, director of engineering at WebTrends. "We do not have any rights outside of the rights that they give us to store and maintain the data for us. It's truly an extension of their organization and ownership of the data. The data is stored in a Tier 4, very secure data center. And the only thing that the customer does is access it through our secure reporting interface and product to gain insight into their data."

Auerbach questions that assertion. "I would suggest that since the collection, aggregation, and conveyance of the data to WebTrends is from the user's computer and not from WhiteHouse.gov that a very strong argument can be made that the data belongs to the user, not WhiteHouse.gov," he said in an e-mail. "If they are, to take the other road, asserting that WhiteHouse.gov owns the data, then we must then recognize that since WhiteHouse.gov is a U.S. federal government entity, [the data] may be governed by the Privacy Act of 1974 and other applicable privacy laws. And those laws constrain the dissemination of government data to private companies unless those companies undertake the same limitations that are imposed upon the government."

Previous
2 of 4
Next
Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading, January 2015
To find and fix exploits aimed directly at your business, stop waiting for alerts and become a proactive hunter.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-7402
Published: 2014-12-17
Multiple unspecified vulnerabilities in request.c in c-icap 0.2.x allow remote attackers to cause a denial of service (crash) via a crafted ICAP request.

CVE-2014-5437
Published: 2014-12-17
Multiple cross-site request forgery (CSRF) vulnerabilities in ARRIS Touchstone TG862G/CT Telephony Gateway with firmware 7.6.59S.CT and earlier allow remote attackers to hijack the authentication of administrators for requests that (1) enable remote management via a request to remote_management.php,...

CVE-2014-5438
Published: 2014-12-17
Cross-site scripting (XSS) vulnerability in ARRIS Touchstone TG862G/CT Telephony Gateway with firmware 7.6.59S.CT and earlier allows remote authenticated users to inject arbitrary web script or HTML via the computer_name parameter to connected_devices_computers_edit.php.

CVE-2014-7170
Published: 2014-12-17
Race condition in Puppet Server 0.2.0 allows local users to obtain sensitive information by accessing it in between package installation or upgrade and the start of the service.

CVE-2014-7285
Published: 2014-12-17
The management console on the Symantec Web Gateway (SWG) appliance before 5.2.2 allows remote authenticated users to execute arbitrary OS commands by injecting command strings into unspecified PHP scripts.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Join us Wednesday, Dec. 17 at 1 p.m. Eastern Time to hear what employers are really looking for in a chief information security officer -- it may not be what you think.