Live data from Hacker News

Cisco Fixes RV320/RV325 Vulnerability by Banning “curl” in User-Agent

twitter.com

91–100 of 322 posts

Re: Cisco Fixes RV320/RV325 Vulnerability by Banning “curl” in User-Agent

#91

User agents shouldn't exist any more. They serve only to help unsuspecting users be fingerprinted.

Rubbish. They are incredibly useful for debugging.

Per https://webkit.org/blog/8042/release-notes-for-safari-techno... the user agent is frozen in webkit now.

Re: Cisco Fixes RV320/RV325 Vulnerability by Banning “curl” in User-Agent

#92

User agents shouldn't exist any more. They serve only to help unsuspecting users be fingerprinted.

Well, the next best thing is what webkit is doing (https://webkit.org/blog/8042/release-notes-for-safari-techno...) by freezing the user agent.

So as time goes by the user agent becomes increasingly homogenous and so, less useful for tracking.

Re: Cisco Fixes RV320/RV325 Vulnerability by Banning “curl” in User-Agent

#93
post #78

Earlier quoted context omitted.

You just wait for Edge-based-on-Chromium's User-Agent :D

Per a buddy who is using said Edgium (Chromium-based Edge): https://i.imgur.com/p6ZMoJY.png

Oh ffs

Re: Cisco Fixes RV320/RV325 Vulnerability by Banning “curl” in User-Agent

#94
post #3

I don't see what the fuss is about. This is an effective mitigation, given that software can't just arbitrarily lie about its user agent.

I guess the biggest problem is that the mitigation isn't future-proof. Someday, there might be other command-line tools besides cURL that can be used for this kind of attack. A better fix would be to just drop all incoming IPv4 packets that have the "evil" bit set. ( https://www.ietf.org/rfc/rfc3514.txt ) Extending this protection to IPv6 is left as an exercise for the reader.

We can claim the LSB of the sequence number.

Re: Cisco Fixes RV320/RV325 Vulnerability by Banning “curl” in User-Agent

#95

Earlier quoted context omitted.

Well at least we acknowledged there's some utility. Now consider that mobile devices are different as well..

The current user agent does not give you much insight about what type of mobile device you have anyway, especially on Android.

I use Firefox for Android on ChromeOS -- it produces interesting results.

Re: Cisco Fixes RV320/RV325 Vulnerability by Banning “curl” in User-Agent

#96
post #15
post #3

I don't see what the fuss is about. This is an effective mitigation, given that software can't just arbitrarily lie about its user agent.

Exactly. Hacking your client to use another user-agent or another IP address is illegal under CFAA. See Craigslist Inc. v. 3Taps Inc. etc...

So when I check desktop site in chrome I'm hacking?

Re: Cisco Fixes RV320/RV325 Vulnerability by Banning “curl” in User-Agent

#97
post #80

Earlier quoted context omitted.

Bob is either a brown-noser or a complete turncoat. Don't be like Bob.

Bob is probably an engineer with twenty years experience, who's been thoroughly ground down by management and peer power-plays and has realised that the best solution is to keep your head below the parapets!

Lol, this is too true. Though I think I learned 80% of this in my first couple months at my first real full time job

Re: Cisco Fixes RV320/RV325 Vulnerability by Banning “curl” in User-Agent

#98
post #75

Earlier quoted context omitted.

There are better solutions available than hanging functionality on unreliable vestigial bits and pieces that shouldn't be there anyway which, because others abuse the functionality, you can't trust to be correct for debugging purposes.

99% of the traffic has the correct user-agent which is useful in tracking down issues that are browser specific. The other 1% will just get ignored as noise. And it's not like we can't tell what type of browser they are using with browser specific objects that we can pull from javascript. We just can't infer the version of the browser which is critical for debugging issues.

I use a randomized user agent and every once in a while get rejected by a site that has decided my browser can't be supported. Usually when I'm on some Safari version. I doubt much effort is being done to identify fake user agents since there are better fruit to pick in the fingerprinting game.

Re: Cisco Fixes RV320/RV325 Vulnerability by Banning “curl” in User-Agent

#99
post #90

Earlier quoted context omitted.

I will never stoop so low as to telegraph my own joke.

I couldn't agree more. The joke construction was a bit weak though, when you miss a good part of the audience. Add something like, "I mean, could you imagine the chaos it would cause if IE told websites it was really Mozilla?" and you demonstrate mastery of the subject matter, which should be enough to let other experts know you were facetious rather than ignorant. Unless you have timing issues... or need the comedia…

I like the original more without your embellishment. The addition sounds like every attempt at follow up humor on reddit.

Re: Cisco Fixes RV320/RV325 Vulnerability by Banning “curl” in User-Agent

#100
post #79

Earlier quoted context omitted.

Rubbish. They are incredibly useful for debugging.

edit: sorry, accidentally submitted early So what. Removing one of the largest sources entropy available for fingerprinting users is important. We shouldn't maintain the terrible long-term effects[1] of tracking everything just to help you have an easier time debugging. [1] http://nymag.com/intelligencer/2019/02/shoshana-zuboff-q-and...

Does it really provide that much entropy? Maybe back in the days when browsers didn’t auto-update, but intuitively it should only provide about four bits at most (os: Android iOS macOS windows, browser: chrome safari edge ie ff) except for a few rare users who don’t stay up to date or choose a weird browser (and those folks probably are a little confused about how privacy works).
Post reply on HN