Every Go application since 1.24 will activate MPTCP on their sockets by default.

And I've read that this includes Syncthing, which is why I'm posting this here

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 4 hours ago* (last edited 4 hours ago) (1 child)

Thank you.

Difficult as in unlikely that the exploit works or difficult to write an exploit? The latter doesn't help me much. :)

Regarding the php2shell issue: a lot of admins took their services down until it was patched. It's more a decision based on a guess - big number bad, evil acronym scary - than actually understanding what the exploit does. One can either believe it or not.

And that's the thing about the recent exploit (multipath TCP): I can't evaluate myself, whether the issue is likely an exploitable RCE. That is one factor missing in risk assessment: is the outcome potentially fatal? Yes, rce and priv escalation. Is it likely? I can't tell.

I'm sorry. I don't mean to doubt your expertise. I simply don't know you. It is the same with hackernews, the author repeats what he's or she's told. (Good overview article though. Thanks again for it.) RN It's: Someone from the internet said don't panic. A link to a statement from the Ubuntu package maintainer or distribution would make me feel at ease. I still couldn't make sure for myself - a lack of time and competence in the field - but I would trust it.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 3 hours ago*

    Difficult as in unlikely that the exploit works or difficult to write an exploit?

    Difficult as in it's a race condition that can theoretically be exploited when you get the timing right. But timing, if it's not on a well-known isolated system right before you in some lab, depends on a million details, some –once we are talking about real-life examples– outside your control.

  • source
  • parent