3 ms·
It's going to be fun if someone finds a security vulnerability in a commonly-emitted-by-LLMs code pattern. That'll be a lot harder to remediate than "Update dep
by Retr0id 11mo ago
It's going to be fun if someone finds a security vulnerability in a commonly-emitted-by-LLMs code pattern. That'll be a lot harder to remediate than "Update dependency xyz"
- MangoToupe 11mo ago> if someone finds a security vulnerability in a commonly-emitted-by-LLMs code pattern how do you distinguish this from injecting a vulnerable dependency to a dependency list?
- Retr0id 11mo agoYou can more easily check for known-vulnerable dependencies
- MangoToupe 11mo agoRight, but if you can embed bad packages in LLMs, you can surely embed any kind of vulnerability imaginable.
- Retr0id 11mo agoI'm not thinking about deliberately embedded vulnerabilities, just accidental/emergent ones. The modern equivalent of devs copy-pasting stackoverflow answers that happen to contain SQL injection vulns.
- MangoToupe 11mo agoDoes the distinction make any difference?
- Retr0id 11mo agoYes, you'd take different actions to avoid each.