• James R Kirk@startrek.website
    link
    fedilink
    English
    arrow-up
    23
    arrow-down
    1
    ·
    20 hours ago

    I have no issue with using AI to find otherwise undiscovered security bugs. But attempting to fixing them with AI I’m not in favor of.

    • The Bard in Green@lemmy.starlightkel.xyz
      link
      fedilink
      English
      arrow-up
      11
      ·
      20 hours ago

      The user’s code is vulnerable to a buffer overflow in certain edge cases. I need to patch the vulnerability and commit the patch to the repo.

      I should rewrite the existing memmanage() function to handle these edge cases. (* Silently removes all other functionality*)

      I should modify garbagecollect() to detect these edge cases. I’ll rename it to garbage_collector() for clarity and readability. (Renames the function, calls it no where)

      Confidently I modified the program as requested, the new version of your application should be more secure and handled memory issues much more efficiently.

      • underscore_@sopuli.xyz
        link
        fedilink
        arrow-up
        10
        ·
        edit-2
        17 hours ago

        /cost

        Total cost: $430.1161

        Total duration (API): 41s

        Total duration (wall): 29m 50s

        Total code changes: 18 786 lines added, 12 lines removed

    • LukeZaz@beehaw.org
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 hour ago

      You seem to be under the impression that AI is a good tool for finding undiscovered security bugs. It’s not. It’s a crapshoot that requires a ton of extra effort to verify. Using it to find bugs wastes time and has a high risk of side-effects, given that AI has no understanding and thus cannot know if an issue is important, if fixing it has unwanted implications, or if there even is one at all. And if you’re going to try to solve that with human supervision, then you may as well just have the human do the review to begin with and leave the AI out of it.