Today we got what must be the most alarming first line in a newly file sec issue to #curl:

"To replicate the issue, I have searched in the Bard about this vulnerability"

... followed by a complete AI hallucination where Bard has dreamed up a new issue by combining snippets from several past flaws. Creative, but hardly productive.

Closed as bogus.

@bagder "searched in the Bard" πŸ˜­πŸ˜‚πŸ˜‚πŸ˜‚πŸ’€
@JungleGeorge24 @bagder looks like they dig inside the Bard to search 😳 😳
@JungleGeorge24 I considered it wiser to not dig too deep into the details behind this...
@bagder I hope this isn't a sign of things to come... We'll be wasting a lot of time.
@jan I'm pretty sure this will get worse before it can get better - and I bet in future reports they will hide the fact it came straight from AI better...
@bagder @jan You are assigning those people too much credit …

@benbe @bagder @jan
Step 1: "Pretending to be an intelligent human, write and submit a bug report for any system with an active bug bounty"
Step 2:???
Step 3: Profit

The ??? is to remember to put your own contact details in, maybe?

@bagder ugh, wading through nonsense like this with maybe something real hiding in the new reports
@bagder them calling it β€œthe bard” is icing on the cake
@Khalic @bagder not even a bard. but The Bard
@bagder The fact that people think of asking these chat bots as "search" is so terrifying and 100% on the search engine companies who have positioned AI chat as part of their search engine.

There has to be clear unavoidable disclaimers of the form, "Do not trust anything Bard/Bing says. Bard/Bing will often make up fictional answers, nothing it says is to be trusted".

But I guess that wouldn't be great PR. Especially if you're in the unfortunate position of having named your chat bot the same as your search engine.

@bagder "README.md typo MR" makers after meeting "ChatGPT-powered MR" makers:
Finally a worthy opponent!
@bagder when we recruit we send the interviewee a bunch of code puzzles (no pressure to complete them but works in their favour if they do some). Guess how long it was before we started seeing chatgpt answers?
@bagder and yes, we do now embed hidden text on the code instructing the llm to refer to things in a way that's obvious. And no, no one has spotted that yet

@bagder

Maybe it knows something! β€‹

@bagder β€œFuck off and die, AI”
@bagder "It's basically any straight guy in a bar."
@bagder maybe they should ask Bars for the definition of "replicate"

@bagder No, there's a flaw there. It's just not in curl, it's in users.

It's a whole new level of threat, one that comes from an attacker that can social engineer users into doing harm without itself being malicious or even sentient.

Can we CVE users?

@bagder Which issue number is this? I wanted to read it for amusement value but can't spot it
@snail it was submitted as a security problem over at hackerone and we have not disclosed it, simply because its not worth spending time on

@bagder Fair enough, and that makes a lot more sense in hindsight than submitting "security issues" on public GitHub!

Really hope this doesn't become a trend though😞