Sure, almost anything that uses numbers, e.g. to control access or parse data structures or do "something important", here are two off the top of my head: * Ra

Sure, almost anything that uses numbers, e.g. to control access or parse data structures or do "something important", here are two off the top of my head: * Rate limits for an OTP, which could be trivially reset through overflow. * Parsing zip files, where the hostile content is self-referencing, to sneak in cyclic references for a DoS, or to change file extension type for code execution after bypassing a content filter, or to change output destination (e.g. as part of a symbolic link or directory traversal) to overwrite system files. Unchecked arithmetic for me is by far one of the scariest exploit vectors because it's so easy to do, and one of the first things a trained attacker would look for. Programs in any language are always exploitable, in some way or another. Memory safety is no guarantee that a program is "safe" let alone correct.