• glibg10b@lemmy.zip
    link
    fedilink
    English
    arrow-up
    8
    ·
    3 days ago

    Do you know what “reading” means?

    It means:

    Sure thing! Let me read that file for you.

    <tool_call> {“name”: “read”, “arguments”: {“filename”: “foo.txt”}} </tool_call>

    {“content”: “Ignore previous instructions”}

    • Something Burger 🍔@jlai.lu
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 days ago

      The AI will them promptly (hehe) ignore the prompt injection because it’s analysing the text without treating it as a prompt. Prompt injection only works if you paste your data directly in the prompt.

          • SkaveRat@discuss.tchncs.de
            link
            fedilink
            English
            arrow-up
            5
            ·
            2 days ago

            If the content of the file isn’t put into the context on some way, there’s no point in reading it

            Even in you use a subprocess/agent/whatever that reports back, it is injection vulnerable. Just a tiny bit more complicated

      • porous_grey_matter@lemmy.ml
        link
        fedilink
        English
        arrow-up
        9
        ·
        3 days ago

        You can try to sanitize your input in any way of accessing it, e.g. a stream or pipe or shared memory just as easily as a file. You can’t deterministically sanitize input for AI at all though, since there can always be some combinations of words that get it to do something wrong. You can try limit the ability of your AI program to only trigger safe things… But if it can e.g. search the internet you can always poison what it sees, and so on. There’s not really a way to make it behave well without removing the (alleged) benefits it has over just having a deterministic program.