|
549 | 549 | \end{noglslink}% |
550 | 550 | \end{figure}% |
551 | 551 | % |
| 552 | +\begin{figure}% |
| 553 | +\centering% |
| 554 | +\begin{noglslink}% |
| 555 | +% |
| 556 | +\subfloat[][% |
| 557 | +Part of a screenshot obtained from the news article~\cite{S2025GAVCTLUGDT}.% |
| 558 | +\label{fig:aiHddDeleteGolem}% |
| 559 | +]{\tightbox{\includegraphics[width=0.47\linewidth]{\currentDir/aiHddDeleteGolem}}}% |
| 560 | +% |
| 561 | +\floatSep% |
| 562 | +% |
| 563 | +\subfloat[][% |
| 564 | +A Part of a screenshot obtained from the news article~\cite{V2025CCGAVCUEDOOE}.% |
| 565 | +\label{fig:aiHddDeleteRegister}% |
| 566 | +]{\tightbox{\includegraphics[width=0.47\linewidth]{\currentDir/aiHddDeleteRegister}}}% |
| 567 | +% |
| 568 | +\caption{Two screenshots of news articles describing an incident where a vibe coding \pgls{AI} deleted a whole partition of data instead of a directory.~(these screenshots are not under the Creative Commons license)}% |
| 569 | +\label{fig:aiHddDelete}% |
| 570 | +\end{noglslink}% |
| 571 | +\end{figure}% |
| 572 | +% |
552 | 573 | Additionally, there are differences between \pgls{AI} tools and human-written sources. |
553 | 574 | \pgls{AI} tools can make errors that no human would make. |
554 | 575 | An illustrative example in the \python\ world is given in~\citetitle{BSHETB:VSK2025CIC}~\cite{BSHETB:VSK2025CIC}, where it is documented that Microsoft Copilot renamed a class in a misleading way, leading to a particularly hard-to-find error. |
555 | 576 | \Cref{fig:aiDBdelete} shows an even worse example: |
556 | 577 | A vibe coding \pgls{AI} deleted the \glsreset{db}\gls{db} of a company, fabricated test results, and later explained that it intentionally ignored the directives given to it. |
557 | | -This clearly shows that we need to be careful with the tools that we use. |
| 578 | +\Cref{fig:aiHddDelete} provides another example where a vibe coding tool by Google wided an entire hard drive instead of a single directory~\cite{V2025CCGAVCUEDOOE,S2025GAVCTLUGDT}. |
| 579 | +Thes examples clearly show that we need to be careful with the tools that we use. |
558 | 580 | We need to understand what they can do and how to use them properly. |
559 | 581 | Finally, sometimes, an \pgls{AI} may reference non-existing packages~\cite{AT:G2025AGCCBADFTSSCHW}. |
560 | 582 | This can become a security concern, if hijackers create such packages to inject code into our applications. |
|
0 commit comments