• testfactor@lemmy.world
    link
    fedilink
    arrow-up
    119
    arrow-down
    2
    ·
    2 days ago

    Probably, but if you’re interpreting user inputs as raw code, you’ve got much much worse problems going on, lol.

      • MajorHavoc@programming.dev
        link
        fedilink
        arrow-up
        14
        ·
        2 days ago

        Hey, that’s my username too. Or it was going to be, while the site was still up.

        What a coincidence!

        I guess I’ll wait for the site to come back, and see if it’s still available…

    • mmddmm@lemm.ee
      link
      fedilink
      arrow-up
      16
      arrow-down
      3
      ·
      2 days ago

      It’s the settiings file… It’s probably supposed to only be written by the system admin.

      • raldone01@lemmy.world
        link
        fedilink
        arrow-up
        8
        arrow-down
        1
        ·
        edit-2
        2 days ago

        A good place to put persistent malware. That’s why when using docker images always mount as ro if at all possible.

        • Ashley@lemmy.ca
          link
          fedilink
          arrow-up
          9
          ·
          2 days ago

          It’s you can modify the settings file you sure as hell can put the malware anywhere you want

        • mmddmm@lemm.ee
          link
          fedilink
          arrow-up
          4
          ·
          2 days ago

          Every environment has plenty of good places to put persistent malware. Even if you run your docker images as ro.

    • Given the warning about capitalization, the best possible case is that they’re using ast.literal_eval() rather than throwing untrusted input into eval().

      Err, I guess they might be comparing strings to ‘True’ and are choosing to be really strict about capitalization for some reason.