Anon (no.delete@this.spam.com) on July 13, 2021 10:07 pm wrote:
> cqwrteur (euloanty.delete@this.live.com) on July 13, 2021 9:49 pm wrote:
> > You say C++ is OO lol. How bad the OO designs are? What about iostream?
>
> I think C++ and it's standard library are bad designed, and that C++ is a bad tool
> for kernel programming, but for sure it is designed as an OO extension of C.
>
> > It is also super safe since there are no virtual tables that can be injected for
> > type confusions. Unlike OO nonsense, which itself is a security vulnerability.
>
> Bullshit again, but I am curious, can you show a know security vulnarability caused by OO?
>
> And please, not something related to C++ which we already know leads to a lot of security
> vulnerabilities, can you show a vulnerability which can also happen in Rust or C#?
>

Because I am a security student following my Ph.D professor. We read papers every day.

The largest reason why C++ is not safe (although it is much safer than C) is because of object-oriented programming.

Type confusions, vptr injection or recent new fancy "COOP" (counterfeit object-oriented programming) attack.

https://www.youtube.com/watch?v=NDt7Tholxp4


You want me to show Rust?

https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=rust

CVE-2020-25575 ** UNSUPPORTED WHEN ASSIGNED ** An issue was discovered in the failure crate through 0.1.5 for Rust. It may introduce "compatibility hazards" in some applications, and has a type confusion flaw when downcasting. NOTE: This vulnerability only affects products that are no longer supported by the maintainer. NOTE: This may overlap CVE-2019-25010.

CVE-2019-25010 An issue was discovered in the failure crate through 2019-11-13 for Rust. Type confusion can occur when __private_get_type_id__ is overridden.