Re:Git Security Vulnerabilities Announced
by unshavedyak on Tuesday January 17, 2023 @04:00PM
(#34419021)
That's most logic issues though, is it not? I agree with you though, i wish Rust more commonly pushed "safer" (not in the UB way) code, like `Vec::get` and `u32::overflow_add` and etc.
Luckily lints help to easily ban the arithmetic/etc ops from projects. Nevertheless i feel it should be a bit closer to Rust's home.
Re:Git Security Vulnerabilities Announced
by dcsommer on Tuesday January 17, 2023 @04:06PM
(#34419126)
Do you have data on the relative frequency and severity of non-memory safety integer overflow security issues?
Re:Git Security Vulnerabilities Announced
by hot_gril on Tuesday January 17, 2023 @08:23PM
(#34422187)
I know at least about the DAO hack.
Re:Git Security Vulnerabilities Announced
by IncRnd on Tuesday January 17, 2023 @10:53PM
(#34423273)
Here are over 3k CVEs that contain "integer overflow". That shouldn't be considered a comprehensive search.
https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=integer+ove...
Re:Git Security Vulnerabilities Announced
by hyperhopper on Wednesday January 18, 2023 @03:18AM
(#34424535)
You don't need to have to have historical stats to show that it can be a security issue.
That's simply not true and has wide-reaching horrible effects that can occur. The wrong number of tickets can be purchased from a website, charging for less than were purchased. The DNR order can be put in place instead of SAVE LIFE. There are countless security issues that can occur.
Saying that integer overflow is only an issue for memory safety is really bad and incorrect advice.