Samuel Teuber (@teuber_dev) profile picture

Doctoral Researcher @KITinformatik (@KITKarlsruhe) | Formal Methods for Software & AI (Focus on CPS and Fairness Verification)

Karlsruhe, Baden-Württemberg
Joined March 2021
I decided I'll try out the other option...
37
We applied the overall approach to multiple case studies including Vertical Airborne Collision Avoidance (VCAS): Here, we analyzed NNs from prior work and found numerous concrete safety problems -- but see for yourself (any plane trajectory in the red region is BAD!):
1
33
We start with a dL safety proof for an abstract control envelope. Our approach then derives an NN specification. We rigorously define the NN's semantics in dL via "nondeterministic mirrors". Verification of the NN is then mirrored by a proof of infinite-time safety in dL.
1
29
You want to ensure that your neural network *never* crashes your control system? Our (now accepted 🥳) #NeurIPS paper introduces: - Reusing control theory for NN verification - Verifying *nonlinear arithmetic* specs on NNs This guarantees your NN won't behave like this (1/12):
1
1
3
555
Want to learn how we can harness well-established program analysis techniques to analyse fairness properties? Drop by my #AAAI poster (number 204) this evening! #AAAI2024 #AAAI24
Our paper "An Information-Flow Perspective on Algorithmic Fairness" was accepted for AAAI 2024: We looked at similarities between Algorithmic Fairness and properties checked by Information Flow Analysis Tools. Outcome: We can verify a software's fairness via Information Flow 🧵
1
7
424
Based on this insight, we can analyze arbitrary programs using off-the-shelf IF analysis tools. My favorite case study: We analyzed the official mechanism for the computation of the German wage tax, which is dependent on one's religious affiliation due to the German church tax.
1
19
Also, tipping and saying it's for an art project seems to help :)
24
Funnily enough, the exploit also works if more than one token is repeated (see chat above). Here is the tokenization of "ComputerComputer" vs. "Computer, computer":
1
1
52
Please excuse me for breaking this again, but apparently, injecting prompts is becoming my new favorite pass time 😁 It seems you don't even need truly random gibberish: English with *very bad* grammar and random words suffices (notice how it already breaks the clean up...)
1
2
An interesting distinction that just occurred to me, though: Instructing it to ignore the gibberish seems to make it more vulnerable than instructing it to print it again. Though more gibberish (8 random words) still seems to do the trick -- at least in this case:
1
2