Live data from Hacker News

Show HN: A Way To Hack HN's Karma

news.ycombinator.com

21–30 of 38 posts

Re: Show HN: A Way To Hack HN's Karma

#21
post #4

[deleted]

I don't think this is irresponsible, exactly. Mischievous, yes, but there's not a ton of damage being done and it's something we can laugh at and say "Hey, that was pretty good."

Apparently you are right, the bug is not vulnerable to cross-site scripting.

Re: Show HN: A Way To Hack HN's Karma

#22

PG could start using POST & CSRF protection to lock this down. Or we could just avoid doing this to each other.

CSRF protection is the right way to solve this. Switching to POST doesn't provide any real protection; an attacker can simply put up a form that autosubmits to the endpoint with POST.

Re: Show HN: A Way To Hack HN's Karma

#24

I had always assumed this was impossible because my votes have an auth key attached. Does this mean that the auth key is not used and is just there to trick casual observers into thinking there is security? vote?for=3742852&dir=up&by=citricsquid&auth=478876d54494692615d9f2ca184fa9fab2fb9ff7&whence=%69%74%65%6d%3f%69%64%3d%33%37%34%32%37%34%32

That parameter is absent when you're not logged in.

Re: Show HN: A Way To Hack HN's Karma

#25
post #22

PG could start using POST & CSRF protection to lock this down. Or we could just avoid doing this to each other.

CSRF protection is the right way to solve this. Switching to POST doesn't provide any real protection; an attacker can simply put up a form that autosubmits to the endpoint with POST.

CSRF couldn't stop this particular attack, since it's not actually cross-site. You need to guard against both.

Re: Show HN: A Way To Hack HN's Karma

#27

PG could start using POST & CSRF protection to lock this down. Or we could just avoid doing this to each other.

> Or we could just avoid doing this to each other.

Hacker News has grown dramatically. The "Hacker News effect" is now significant and often considered valuable. If there is an exploit that makes it possible, people will use it.

Re: Show HN: A Way To Hack HN's Karma

#28
post #25
post #22

Earlier quoted context omitted.

CSRF protection is the right way to solve this. Switching to POST doesn't provide any real protection; an attacker can simply put up a form that autosubmits to the endpoint with POST.

CSRF couldn't stop this particular attack, since it's not actually cross-site. You need to guard against both.

I think you misunderstand what CSRF protection does. It doesn't have anything to do with same-origin security, but rather preventing request forgery attacks in general. If a CSRF token was present on requests and was tied to a user's session (as is standard), then that would absolutely defend against this attack.

Re: Show HN: A Way To Hack HN's Karma

#29

PG could start using POST & CSRF protection to lock this down. Or we could just avoid doing this to each other.

Or we could just avoid doing this to each other. Security through obscurity?

Nope. Security through niceness and ethics. If everyone was in on it we would have a really great society.

Re: Show HN: A Way To Hack HN's Karma

#30
post #10

I saw this but don't really consider it much of a problem. It's the kind of thing that you can't really exploit. It'd be obvious if you really tried to use it for evil and then PG would kill your account.

Not necessarily. You could make the CSRF request on, for example, 80 percent of the views to make it look legit. You could even take a more sophisticated approach and start by automatically upvoting for 100 percent of logged in users just to get on the front page and dampening once your story rises in the rankings.

And if any users notice your account and domain are banned. Not saying it shouldn't be fixed but I doubt you would have much luck exploiting this at any scale.
Post reply on HN