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
Latest Comment: nice post
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-1950
Published: 2015-07-01
IBM PowerVC Standard Edition 1.2.2.1 through 1.2.2.2 does not require authentication for access to the Python interpreter with nova credentials, which allows KVM guest OS users to discover certain PowerVC credentials and bypass intended access restrictions via unspecified Python code.

CVE-2015-1951
Published: 2015-07-01
IBM Maximo Asset Management 7.1 through 7.1.1.13, 7.5.0 before 7.5.0.8 IFIX001, and 7.6.0 before 7.6.0.0 IFIX005 does not prevent caching of HTTPS responses, which allows physically proximate attackers to obtain sensitive local-cache information by leveraging an unattended workstation.

CVE-2015-1967
Published: 2015-07-01
MQ Explorer in IBM WebSphere MQ before 8.0.0.3 does not recognize the absence of the compatibility-mode option, which allows remote attackers to obtain sensitive information by sniffing the network for a session in which TLS is not used.

CVE-2014-9734
Published: 2015-06-30
Directory traversal vulnerability in the Slider Revolution (revslider) plugin before 4.2 for WordPress allows remote attackers to read arbitrary files via a .. (dot dot) in the img parameter in a revslider_show_image action to wp-admin/admin-ajax.php.

CVE-2014-9735
Published: 2015-06-30
The ThemePunch Slider Revolution (revslider) plugin before 3.0.96 for WordPress and Showbiz Pro plugin 1.7.1 and earlier for Wordpress does not properly restrict access to administrator AJAX functionality, which allows remote attackers to (1) upload and execute arbitrary files via an update_plugin a...

Dark Reading Radio
Archived Dark Reading Radio
Marc Spitler, co-author of the Verizon DBIR will share some of the lesser-known but most intriguing tidbits from the massive report