Re:This shouldn't have happened: A vulnerability postmortem
by foobiekr on Wednesday December 01, 2021 @10:27PM
(#29412204)
I don’t disagree with you. But just before writing that message I was code reviewing some python that was vulnerable a to the most basic SQL injection. Who needs or wants execution authority when you can dump the users table of salted sha passwords?
[ Parent
| on HN ]
Re:This shouldn't have happened: A vulnerability postmortem
by saagarjha on Thursday December 02, 2021 @01:01AM
(#29413030)
In C you can just use code execution to grab the passwords before they get salted…
Re:This shouldn't have happened: A vulnerability postmortem
by foobiekr on Thursday December 02, 2021 @02:51AM
(#29413583)
One is the whole database.
I am very aware of code execution attacks and persistence around them. C has a class of failures that are not present in most other languages that are in current use, my point is that it really only solves part of the problem.
From a security perspective, the 90% issue is the poor quality of developers in whatever language you choose.
Re:This shouldn't have happened: A vulnerability postmortem
by nicoburns on Thursday December 02, 2021 @05:01AM
(#29414344)
I think the difference is in the difficulty in preventing the bugs. I'd be very surprised if our codebase at work contained SQL injection bugs. We use a library that protects against them by default, and all code gets reviewed by a senior developer. SQL injection is easy to prevent with a simple code review process.
Subtle issues with undefined behaviour, buffer overflows, etc in C are much trickier and frequently catch out even highly experienced programmers. Even with high quality developers your C program is unlikely to be secure.