3 ms·
A vulnerability? Yes. A serious one... i don't really think so in the grand scheme of things. Injection vulnerabilities in one form or another are like 90% of
by bawolff 4y ago
A vulnerability? Yes. A serious one... i don't really think so in the grand scheme of things.
Injection vulnerabilities in one form or another are like 90% of all security vulnerabilities. We have the obvious ones like sql injection or shell injection. We dont call XSS injection but it really is just html/js injection. Even things like buffer overflows are injections if viewed through the right lens.
If there is one thing the security field has learned from all this, its that blacklist approaches to security are a pain and almost never work. Especially for complex input formats.
- simonw 4y agoThere's a crucial difference between prompt injection and other injection attacks such as SQL injection or XSS or shell injection. For all of those other injection attacks we know what the mitigations are: parameterized queries for SQL injection. Context-aware HTML escaping for XSS. Shell special character escaping for shell commands. Prompt injection does not have a reliable mitigation yet. It's currently an injection attack without a fix.
- bawolff 4y agoWell its been a long time for lots of these. The original xss security advisory had the non-sensical advice that "Web Users Should Not Engage in Promiscuous Browsing". [1] But anyways, that's kind of my point. When people try and fix xss by just blacklisting some tags they think are bad instead of proper escaping, it never works. Which is basically where we are at with mitigations for prompt injection, so similiarly it probably wont work here. [1] https://web.archive.org/web/20020124063448/www.cert.org/advisories/CA-2000-02.html https://web.archive.org/web/20020124063448/www.cert.org/advi...