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.

Operational Security

8/23/2017
06:16 PM
Curtis Franklin
Curtis Franklin
Curt Franklin
50%
50%

DoJ Narrows Scope of DreamHost Warrant

The Department of Justice has scaled back the demands of a search warrant served to web hosting provider DreamHost.

When most IT managers think about cybersecurity, they're thinking about keeping their company's data safe from criminals and cyber-warfare opponents. Some service providers, most recently DreamHost, have expanded that list of adversaries to include the US Department of Justice. And on August 22, DreamHost scored a small victory in their most recent battle.

If you haven't been following this particular part of the news, back in July the Department of Justice obtained a federal warrant ordering DreamHost to turn over everything they had regarding www.disruptj20.org, a site hosted on the company's computers. DreamHost declined, stating that to do so would mean giving the DoJ (among other things) the IP address, and therefore a huge hint about the identity, of everyone who had ever visited the site.

Since approximately 1.3 million people had visited the site, and only 239 were arrested in the protest organized by the site, DreamHost stated that this meant the Fourth Amendment rights of approximately 1.3 million people would be violated. According to some legal analysis, DreamHost's objections are unusual since a two-step warrant process is normal.

In this two-step process, the government asks for, and receives, everything possible from a provider, then sorts through the information and throws away everything not specific to the original warrant. DreamHost objected to providing the first step because of the political nature of the site.


Want to learn more about the technology and business opportunities and challenges for the cable industry in the commercial services market? Join Light Reading in New York on November 30 for the 11th annual Future of Cable Business Services event. All cable operators and other service providers get in free.

Yesterday, news broke that the Department of Justice has scaled back its request for information. In a legal brief filed this morning, the U.S. attorney for the District of Columbia, Channing Phillips, wrote, "the Warrant was not intended to be used, and will not be used, to 'identify the political dissidents of the current administration[.]'... Nor will it be used to 'chill... free association and the right of free speech afforded by the Constitution.' "

The brief then goes on to say, "One of those challenges is that some of the evidence -- particularly the full scope of the evidence -- will be hidden from the government's view unless and until the government obtains a court order or search warrant." Translated into English, that means that the government doesn't know precisely what it's looking for until it sees everything you have. While common in cyber-warrants, this is the opposite of the logic used in most physical evidence warrants.

The DoJ said that it didn't realize that, in asking for everything DreamHost had, it would get log files that included IP addresses and has no desire to identify those who simply visited the site. DreamHost, for its part, stated in a blog post that, while it welcomes the DoJ's revisions, it doesn't believe they go far enough. DreamHost promises that it will lay out additional objections and seek further narrowing of the warrant in court proceedings on the morning of Thursday, August 24.

Disclosure: The author is a long-time customer of DreamHost and continues to host websites and email services with the company.

— Curtis Franklin is the editor of SecurityNow.com. Follow him on Twitter @kg4gwa.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
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
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...