Remote Prompt Injection in Gitlab Duo Leads to Source Code Theft

19 chillax 5 5/23/2025, 7:12:33 AM legitsecurity.com ↗

Comments (5)

mdaniel · 2m ago
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
cedws · 4h ago
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.
hu3 · 3h ago
I would have the same caution, if my code was any special.

But the reality is I'm very well compensated to summon CRUD slop out of thin air. It's well tested though.

I wish good luck to those who steal my code.

nusl · 5h ago
GitLab's remediation seems a bit sketchy at best.
reddalo · 4h ago
The whole "let's put LLMs everywhere" thing is sketchy at best.