|
|
|
|
|
by wolftickets
945 days ago
|
|
[I work at Protect AI] You're spot on for data being the jugular, interestingly with exploits like this as an attacker you could quickly go for attacking model content but also have credentials that would grant you access to data in many cases. These tools can serve as the first opening but a sizable one when looking to attack an enterprise more broadly. |
|
Suppose someone magically creates thousands of repositories that write about a specific way of doing c pointers but all allow for buffer overflows, or sql queries with subtle ways to inject strings.
One way to defend is each data source that goes into training is to have an ai agent asses the input sources.
But even so it’s extremely difficult to catch convoluted attacks (ie when an exploit can be made upon meeting certain criteria).
Until then i’d consider any code written by an ai and unsupervised by a competent person as potentially tainted.