• nathris@lemmy.ca
    link
    fedilink
    arrow-up
    13
    ·
    1 year ago

    Could be an RCE exploit. Doesn’t matter if it’s privilege escalation at that point because it can be used to execute a payload that can.

    • taaz@biglemmowski.winOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      1 year ago

      To top it of it seems it’s also contained in libcurl, and getting RCEd just by doing a request does not sound fun.

    • PowerCrazy@lemmy.ml
      link
      fedilink
      arrow-up
      2
      arrow-down
      6
      ·
      1 year ago

      I’ll admit i’m out of my depth about exactly how curl works on the local system, but surely if there is a vulnerability in the “libcurl” library that is much more serious and severe then just saying “curl” is vulnerable.

      I’m assuming that libcurl touches a huge amount of the linux network stack.

      • tony@lemmy.hoyle.me.uk
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        They specifically say the high vulnerability one affects the command line tool, not just the library. High implies privilege escalation… I’m wondering how at this point because it’s not setuid and there’s really no reason opening a TCP socket could cause it (and if it does, that’s a kernel error not curl).