|No such thing as a small change|
Re^4: Perl Security Testingby marto (Archbishop)
|on Jul 26, 2017 at 09:49 UTC||Need Help??|
Don't flatter yourself, difficult for you I know.
"The OP knows little about security"
Interesting you should say that about others, given your post history on the subject.
"First, that there is nothing particularly special ... nor, categorically “vulnerable,” about Perl."
"This flaw could be exploited to carry out a denial of service attack against code that uses arbitrary user input as hash keys.". Perl might allow context-dependent attackers to bypass the taint protection mechanism in a child process via duplicate environment variables in envp..
"Merely overflowing a buffer will not get you root, and so on."
"Exploiting the behavior of a buffer overflow is a well-known security exploit. On many systems, the memory layout of a program, or the system as a whole, is well defined. By sending in data designed to cause a buffer overflow, it is possible to write into areas known to hold executable code, and replace it with malicious code. Buffers are widespread in operating system (OS) code, so it is possible to make attacks that perform privilege escalation and gain unlimited access to the computer's resources. The famed Morris worm used this as one of its attack techniques."
get a root shell via buffer overflow privilaged escalation of lpr, among many others.
"I will also, incidentally, stand behind all of my previous, cited by you, posts, as well."
The crux of the problem. Your attitude. You stand by your terrible advice that has been proven wrong, time and time again. You hold your head up high and stand by what is proven incorrect. You don't care. Self publicising against all else. Regarding the human factor, you're just spouting what you think people want to hear, all other examples linked to many times before show you behaving in the opposite manner in which you claim.