News for hackers. Stuff that matters.
Re:Disclosing vulnerabilities to protect users by voltagex_ on Monday October 31, 2016 @07:35PM (#12841953)
Does anyone know which version of Chrome this was fixed in? This may force $EMPLOYER to finally update from an unholy mix of 50 and 53.
Re:Disclosing vulnerabilities to protect users by leesalminen on Monday October 31, 2016 @07:47PM (#12842021)
If you rely on printing things, don't update to Chrome 54.

https://bugs.chromium.org/p/chromium/issues/detail?id=658606

Re:Disclosing vulnerabilities to protect users by voltagex_ on Monday October 31, 2016 @07:53PM (#12842061)
Christ, Google. At least the workaround is relatively simple - print to PDF (using Chrome's built in option) and then print that from another reader.
Re:Disclosing vulnerabilities to protect users by 15thandwhatever on Monday October 31, 2016 @10:27PM (#12842907)
Edit: I deleted my original comment because I totally confused the brands (Xerox, not Brother). Brother doesn't do rebranded Samsung printers.

Link to Xerox issue: http://www.dkriesel.com/en/blog/2013/0802_xerox-workcentres_...

Re:Disclosing vulnerabilities to protect users by jrowley on Monday October 31, 2016 @07:46PM (#12842014)
Why would your employer fix you to a specific version of chrome? Thats bizarre.
Re:Disclosing vulnerabilities to protect users by acdha on Monday October 31, 2016 @10:56PM (#12843016)
Never underestimate the degree to which enterprise IT departments view change as something to be feared. I once heard someone say that they wanted to delay Chrome updates until their security team could review them — said review process basically being waiting in a backlog for weeks and then someone searches for CVEs posted on that version.
Re:Disclosing vulnerabilities to protect users by technion on Tuesday November 01, 2016 @05:49AM (#12844418)
I worked with a Government group that firmly rejected the concept of Windows security updates.

The general premise was, if you apply an update and something breaks (note that "changed behaviour" means "broken"), someone's head will roll. If you do nothing and get compromised, it's those damned <country> hackers again.

Re:Disclosing vulnerabilities to protect users by nailer on Tuesday November 01, 2016 @05:07AM (#12844272)
> Never underestimate the degree to which enterprise IT departments view change as something to be feared.

This. These supposedly risk-averse organisations also have no concept of the risk of stasis, only the risk of change.

Re:Disclosing vulnerabilities to protect users by protomyth on Tuesday November 01, 2016 @11:00AM (#12846150)
> Never underestimate the degree to which enterprise IT departments view change as something to be feared.

Never underestimate the management's ability to fire a Enterprise IT workers for applying an update that the developer's swear changes no behavior in the companies enterprise software, but actually does.

// been on both sides, we suck at testing and risk assessment in this profession

Re:Disclosing vulnerabilities to protect users by acdha on Tuesday November 01, 2016 @11:24AM (#12846524)
Definitely — when you see people afraid to do something, that almost always indicates a deeper organization problem.
Re:Disclosing vulnerabilities to protect users by cesarb on Monday October 31, 2016 @07:59PM (#12842097)
Large companies tend to be bad at keeping up-to-date. I know of a bank that still uses OpenOffice. No, not Apache OpenOffice: they still use the real OpenOffice.org.

Workstations are often locked down, so employees can't install or upgrade anything.

Re:Disclosing vulnerabilities to protect users by ajdlinux on Monday October 31, 2016 @08:03PM (#12842129)
A friend of mine working for the government told me that in one major government agency, the most popular version of IE used on their website is IE11.

The second most popular version? IE 6. Not even 8. IE 6.

Who still uses it? Employees of other government departments...

Re:Disclosing vulnerabilities to protect users by konklone on Monday October 31, 2016 @10:41PM (#12842954)
While this is plausible for the past, I think this info is outdated now. https://analytics.usa.gov has lots of data on this (and you can break it out by agency using the dropdown at the top). It also estimates that only 5% of data comes from federal networks.

(Disclaimer: I work on analytics.usa.gov.)

Re:Disclosing vulnerabilities to protect users by ajdlinux on Monday October 31, 2016 @10:44PM (#12842970)
I didn't say US Government. Australia :)
Re:Disclosing vulnerabilities to protect users by konklone on Monday October 31, 2016 @11:44PM (#12843215)
Re:Disclosing vulnerabilities to protect users by voltagex_ on Tuesday November 01, 2016 @06:57AM (#12844636)
Re:Disclosing vulnerabilities to protect users by voltagex_ on Monday October 31, 2016 @11:39PM (#12843185)
We should have analytics.dto.gov.au.
Re:Disclosing vulnerabilities to protect users by angry_octet on Tuesday November 01, 2016 @08:18AM (#12845016)
This is because some project once created an internal application with a web interface, which was tested with IE6. This application may be critical to keeping people happy (e.g. the HR system) or some unqualified bozo may want to 'cut costs' like updating apps to new browsers, so mandates sticking to a 'stable' version like IE6. And all future apps will have to target IE6 forever more...

It gets worse... People write apps that use Flash (online training) or Java applets.

There are solutions to this, but none of them involve using the one true SOE, one SOE to rule them all!

Re:Disclosing vulnerabilities to protect users by tjalfi on Tuesday November 01, 2016 @12:31AM (#12843438)
I would hope that they are using IE11 set to IE6 compatibility mode. My employer has an application that requires IE5 compatibility mode.
Re:Disclosing vulnerabilities to protect users by alanh on Monday October 31, 2016 @08:17PM (#12842244)
Yeah… just a reminder: IE6 was released in August 2011.
Re:Disclosing vulnerabilities to protect users by kpozin on Monday October 31, 2016 @08:24PM (#12842301)
A little earlier than that: August 2001.
Re:Disclosing vulnerabilities to protect users by alanh on Tuesday November 01, 2016 @12:00AM (#12843300)
Can I blame bitrot? Yes, thanks, of course I meant 2001.
Re:Disclosing vulnerabilities to protect users by madgar on Tuesday November 01, 2016 @09:38AM (#12845580)
For a sense of just how long ago that was, IE6 was released before 9/11. Truly a more innocent time.
Re:Disclosing vulnerabilities to protect users by Diggsey on Monday October 31, 2016 @08:23PM (#12842291)
No it wasn't... It was released in 2001
Re:Disclosing vulnerabilities to protect users by drv on Monday October 31, 2016 @08:24PM (#12842302)
2001, not 2011. Time flies. :)
Re:Disclosing vulnerabilities to protect users by peterwwillis on Monday October 31, 2016 @08:17PM (#12842242)
Even if the employee can update it themselves, it is often prohibited, and fixing a vulnerability is treated as unauthorized installation of software, which is clearly against the terms of employment when using company computers. Whether they treat it as a big deal or not depends on who is involved, of course.
Re:Disclosing vulnerabilities to protect users by shthed on Tuesday November 01, 2016 @10:10AM (#12845831)
Java applets! I know a government department that'll be stuck on Chrome 44 for a looong time.
Re:Disclosing vulnerabilities to protect users by protomyth on Tuesday November 01, 2016 @11:02AM (#12846177)
Someone could make a mint selling a Java applet runner to government agencies.
Re:Disclosing vulnerabilities to protect users by woliveirajr on Monday October 31, 2016 @11:31PM (#12843142)
I (anecdote) know a country- sized governamental system that sticks to specific versions of Firefox. Not chrome or edge or IE or Safari or... Just Firefox. Specific versions. With some big lag when new versions of Firefox come out.

Companies and citizens, live with that.

Re:Disclosing vulnerabilities to protect users by voltagex_ on Monday October 31, 2016 @11:33PM (#12843151)
Firefox has the ESR release for this purpose.
Re:Disclosing vulnerabilities to protect users by woliveirajr on Tuesday November 01, 2016 @09:15PM (#12851565)
Yes, thanks for this information.

But sadly no, they don't follow this kind of stable release.

Re:Disclosing vulnerabilities to protect users by voltagex_ on Monday October 31, 2016 @07:47PM (#12842016)
Yes, yes it is.
Re:Disclosing vulnerabilities to protect users by revelation on Monday October 31, 2016 @07:52PM (#12842056)
None of the vulnerabilities are in Chrome?
Re:Disclosing vulnerabilities to protect users by voltagex_ on Monday October 31, 2016 @07:55PM (#12842075)
Google says their sandbox prevents it, but https://helpx.adobe.com/security/products/flash-player/apsb1... says Chrome's embedded Flash is affected.
Re:Disclosing vulnerabilities to protect users by revelation on Monday October 31, 2016 @08:01PM (#12842110)
I think they update that separately from Chrome versions. My Chrome already updated to 54 so I can't verify that, but you can check chrome://plugins/ to see if you have the fixed 23.0.0.205 version.