We disclosed this #hackerone report against #curl when someone asked Bard to find a vulnerability, and it hallucinated together something:
We disclosed this #hackerone report against #curl when someone asked Bard to find a vulnerability, and it hallucinated together something: 18 comments
@bagder This is why you can never trust a #LLM... They dump so much #inaccurate #information or even #wrong information :( @bagder “I have searched in the Bard about this vulnerability”. Right there is the problem. LLMs are not search engines. This is similar to the attorney that “searched” for case law using ChatGPT and ended up filing a legal argument full of references to made up cases. @bagder@mastodon.social thanks for posting this, i needed a chuckle with my morning coffee!! @bagder it’s all the weirder because they aren’t even trying to report a new vulnerability. Their complaint seems to be that detailed information about a “vulnerability” is public. But that’s how public disclosure works? And open source? Like are they going to start submitting blog posts of vulnerability analysis and ask curl maintainers to somehow get the posts taken down??? @derekheld they reported this before that vulnerability was made public though @bagder Bard doing bard things - writing entertaining stories that are nothing more than myth. All it needs is a lute and a penchant for rough taverns. @bagder I suspect the reporter's last comment in that thread was also written by an LLM @bagder I could understand using some kind of AI to get something similar to a fuzzer but this is utterly ridiculous…
|
@bagder And the report is that the fixes for the vulnerability are posted on the Internet? This is so ridiculous.