News for hackers. Stuff that matters.
Re:Comma Separated Vulnerabilities by paultopia on Monday June 05, 2017 @03:44PM (#14490869)
The really infuriating thing about this report is the message these terrible applications give to users. "Links to other files?" And the inquiry about whether those "links" should be "updated?" That's a ridiculous, terrible, message to express "remote code execution." Just as bad is "automatic update of links."

The hell? If I were reading this (as a sophisticated user who isn't a security expert), I'd just assume there was some kind of weird document embedding thing going on. Not that "link to other file" meant "RUN ARBITRARY APPLICATIONS AND PROBABLY EXECUTE ARBITRARY CODE."

Even the warning about "To access this data Excel needs to start another application" is incredibly deceptive. The data in a CSV is perfectly damn accessible without Excel opening anything else. It ought to say "to execute the commands embedded in this data, Excel needs to start another application," so that people bloody well know that they're not just viewing data but they're actually doing something.

Horrible, horrible, horrible communication.

Re:Comma Separated Vulnerabilities by jancsika on Monday June 05, 2017 @08:15PM (#14493610)
> It ought to say "to execute the commands embedded in this data, Excel needs to start another application," so that people bloody well know that they're not just viewing data but they're actually doing something.

That's an astute observation.

Somewhat related:

Awhile back I remember seeing a demo of some Mozilla tech that would let one rotate a web page and then view a 3d "stack" of all the DOM elements. A bit like each layer was made up of different colors of lego blocks.

Is there some similar visualization tool to help distinguish data from code?

For example, imagine I want to use some scissors to clip some daisies on a hilltop. I eyeball the daisies I want. When I pick up the scissors they snap a picture of the daisies and cut 1000ft below until they split into the bedrock. Consequently, a demon's fiery arm shoots out the hole holding my scissors, violently cuts the daisies, then picks them up and offers them to me as a low, rumbling voice announces: "Daisies."

Now I don't know about anyone else, but I think that experience would make me a wee bit cautious about picking flowers. Or at least more than I would be merely by reading a man page.

Edit: I guess to be sensible, the demon's arm would need to recede back into the bedrock and heal the split.

Re:Comma Separated Vulnerabilities by floatboth on Tuesday June 06, 2017 @11:00AM (#14497722)
3D stack of DOM elements wasn't just a tech demo, it was actually part of the devtools. Removed because no one reimplemented it in a way that's compatible with multiprocess Firefox https://bugzilla.mozilla.org/show_bug.cgi?id=1086492
Re:Comma Separated Vulnerabilities by gleenn on Tuesday June 06, 2017 @11:52AM (#14498147)
An amazing feature which was moved to a still accessible extension. Sadly I can't remember the name right now but I found it very recently. Makes understanding HTML nesting rapidly apparent.
Re:Comma Separated Vulnerabilities by technomalogical on Tuesday June 06, 2017 @02:12PM (#14499581)
Re:Comma Separated Vulnerabilities by floatboth on Tuesday June 06, 2017 @06:51PM (#14502179)
Yes. (And it does not work with e10s.)
Re:Comma Separated Vulnerabilities by Arnavion on Monday June 05, 2017 @04:38PM (#14491709)
>"Links to other files?" And the inquiry about whether those "links" should be "updated?" That's a ridiculous, terrible, message to express "remote code execution."

There is a document embedding feature in Office documents. Perhaps OO is just reusing the same warning for both situations.

Re:Comma Separated Vulnerabilities by averagewall on Monday June 05, 2017 @06:47PM (#14492983)
I agree. I've seen these warnings from time to time and assumed like you did that the other person had linked to another spreadsheet or used OLE or something. I clicked no because I was sure I didn't have whatever other file it might be linking to, not because I was concerned it might be insecure.
Re:Comma Separated Vulnerabilities by userbinator on Monday June 05, 2017 @11:26PM (#14494517)
I'd just assume there was some kind of weird document embedding thing going on.

If you know the basics of OLE[1] you'd be aware that running another application is the entire concept behind how it all works --- and in this context, the warning message isn't all that bad: note that it says "Remote data not accessible", suggesting it's not the data in the CSV itself. Furthermore, the final sentence asks whether to start CMD.EXE, which should hopefully surprise you enough into clicking No.

[1] https://en.wikipedia.org/wiki/Object_Linking_and_Embedding

Re:Comma Separated Vulnerabilities by Piskvorrr on Tuesday June 06, 2017 @06:05AM (#14496049)
"If you know the murgle gurgle flurgle..." never mind, you've already lost the attention of 99.99999% of Excel users. As for the others, I know what OLE is (to the tune of "a big gaping security hole"), yet I still find the wording incredibly confusing.
Re:Comma Separated Vulnerabilities by paultopia on Tuesday June 06, 2017 @12:50PM (#14498719)
Yeah, exactly. And, I'd add, the attention even of sophisticated Excel users who don't actually write code for Windows.