▲ | Remote Prompt Injection in Gitlab Duo Leads to Source Code Theft(legitsecurity.com) | ||||||||||||||||
21 points by chillax 9 hours ago | 6 comments | |||||||||||||||||
▲ | cedws 6 hours ago | parent | next [-] | ||||||||||||||||
Until prompt injection is fixed, if it is ever, I am not plugging LLMs into anything. MCPs, IDEs, agents, forget it. I will stick with a simple prompt box when I have a question and do whatever with its output by hand after reading it. | |||||||||||||||||
| |||||||||||||||||
▲ | mdaniel an hour ago | parent | prev | next [-] | ||||||||||||||||
Running Duo as a system user was crazypants and I'm sad that GitLab fell into that trap. They already have personal access tokens so even if they had to silently create one just for use with Duo that would be a marked improvement over giving an LLM read access to every repo in the platform | |||||||||||||||||
▲ | nusl 6 hours ago | parent | prev [-] | ||||||||||||||||
GitLab's remediation seems a bit sketchy at best. | |||||||||||||||||
|