News for hackers. Stuff that matters.
Re:Google's login page accepts a vulnerable GET parameter by tptacek on Tuesday August 30, 2016 @11:35PM (#12395841)
I feel like the industry has had a long time to consider both XSS and open redirects, and has come to a pretty firm conclusion on the severity ratings for each of those classes.

I'll sum it up as: "Google is not outside of the mainstream in their assessment."

Re:Google's login page accepts a vulnerable GET parameter by justonepost on Tuesday August 30, 2016 @11:57PM (#12395929)
Re:Google's login page accepts a vulnerable GET parameter by tptacek on Wednesday August 31, 2016 @12:06AM (#12395950)
CVSS is a ouija board. You can make it say whatever you want.

I strongly recommend people avoid CVSS. Pentesters with clients that require CVSS in reports spend an extra couple minutes on every vuln in that silly calculator trying to figure out how to make XSS come out to sev:med and logout CSRF to sev:info.

Re:Google's login page accepts a vulnerable GET parameter by blazespin on Wednesday August 31, 2016 @12:43AM (#12396090)
CVSS is an ouija board .. You can't make it say whatever you want. Each item has pretty well documented constraints.

It's not great, but do you have something better?

Re:Google's login page accepts a vulnerable GET parameter by dsacco on Wednesday August 31, 2016 @01:15AM (#12396167)
Severity rating is a highly contextual process, for which CVSS fails magnificently. Not only is it devoid of context (is this CSRF on private messaging or password reset?), it is not consistent.

If you browse the vulnerabilities listed by CVSS for random Linux utilities, for example, you'll find the same vulnerability listed several times with different ratings despite them apparently having the same exploitation requirements and final impact ("authentication not required, remote attacker, potential user data compromise", etc).

Then it will generally go on to give a vague explanation that is absent any real exploitation details and simply link to five different websites that all copy-pasted the same SecLists disclosure verbatim.

Basically, it's crap, and it exists because the information security industry is bifurcated into two different industries - the risk folks and scanner Rockies who don't have any real technical competency but who love to have things like the CISSP and those who actually know what they're doing in the trenches of technical penetration testing and security audits.

The industry unfortunately attracts two distinct crowds - people who can and do develop actual software, but who specialize in security, and people who can talk the talk and have a vested interest in the pomp that comes along with crappy guidelines.

If you asked a real vulnerability researcher like Tavis Ormandy to CVSS score any of his findings, he'd probably laugh. His disclosures are usually verbose precisely because this is an industry that should be nuanced.

Just because we have nothing better does not mean we should heed an abysmal system.

Re:Google's login page accepts a vulnerable GET parameter by ebbv on Tuesday August 30, 2016 @11:37PM (#12395853)
Yeah, and WordPress is not outside the mainstream in their views on security either but they're wrong (which is constantly proven by how often WordPress sites get compromised.)

Part of my comment was directed at the fact that the mainstream standards of security for web developers (speaking as one myself) are too low.

Re:Google's login page accepts a vulnerable GET parameter by tptacek on Tuesday August 30, 2016 @11:40PM (#12395865)
This is a non sequitur.

Also: WordPress is far outside the mainstream of security practice; they are, and have been for coming up on a full decade, a running joke in the field.

Nobody says that about Google.

Re:Google's login page accepts a vulnerable GET parameter by tnorthcutt on Wednesday August 31, 2016 @12:13AM (#12395974)
This is a bit off-topic, but can you expand on this with regard to WordPress, or possibly link to someone who has? I work with WordPress and would be eager to learn more about where & how it's deficient, and how to guard against those deficiencies better.
Re:Google's login page accepts a vulnerable GET parameter by Tushon on Wednesday August 31, 2016 @03:30AM (#12396563)
Re:Google's login page accepts a vulnerable GET parameter by ebbv on Tuesday August 30, 2016 @11:43PM (#12395878)
WordPress is the mainstream of web development. It's not a non-sequitur because you brought up "the mainstream".

If you're saying that you meant the mainstream of security professionals specifically, I'd be interested in what a survey of security professionals had to say about open redirect. For me it's clearly a potential attack vector, and Google's specific implementation is obviously sloppy and lazy. I can't see any security professional worth their salt giving it a pass.

As far as Google not being a running joke, that's true and it's all the more reason it's surprising they are so dismissive of concerns about their way too broad whitelist.

Re:Google's login page accepts a vulnerable GET parameter by tptacek on Tuesday August 30, 2016 @11:46PM (#12395887)
I feel like at this point we both understand the point I was making and don't need to litigate it further. You can and should feel free to disagree with it, but there's a reason pentesters file open redirects sev:lo.

(XSS is the canonical sev:medium, for what it's worth).

Re:Google's login page accepts a vulnerable GET parameter by throwaway5752 on Wednesday August 31, 2016 @12:00AM (#12395934)
x
Re:Google's login page accepts a vulnerable GET parameter by ebbv on Wednesday August 31, 2016 @12:16AM (#12395988)
Man if you are afraid to disagree with someone just because of who they are I feel bad for you. I've let pg have it on here when I disagreed with him. It doesn't matter. Everybody's wrong sometimes.
Re:Google's login page accepts a vulnerable GET parameter by tptacek on Wednesday August 31, 2016 @12:20AM (#12396004)
I'm one of your downvoters. :)