Skip to main content
13 events
when toggle format what by license comment
Jun 11, 2017 at 10:09 comment added CodesInChaos Deserializing untrusted data using serializers designed for trusted data is one of my favourites.
Jan 27, 2017 at 5:11 vote accept the_endian
Jan 26, 2017 at 22:31 answer added FMaz timeline score: 1
Jan 26, 2017 at 22:03 comment added the_endian @Krazor awesome thanks. Well if you want to post an official answer with examples I would accept it . I don't want to make you do it here in the comments!
Jan 26, 2017 at 21:57 comment added FMaz Here's a short list of situations which I'm always on the lookout for: Improper input validation, uncatched exceptions, use of 'insecure' functions, (such as pythons eval, I actually grep these when doing source-known projects), Race Conditions, DevEnv vs Production Environment errors, developers misunderstanding of documentation, and the list goes on. I can give you examples if I communicated some of these badly.
Jan 26, 2017 at 21:48 comment added the_endian @Krazor when you say logic errors, you're talking about something such as fail to check input validation properly or fail to take certain circumstances into account?
Jan 26, 2017 at 21:46 comment added FMaz I can totally relate to the issue you're currently facing. There was a time where I just wouldn't see how all these complex memory vulnerabilities could be translated over to a memory-safe language. Now while there are exploits like the aforementioned CVEs or the PHP exploit that pornhub.com rewarded with 10000$, I've found that it's the logic errors, which really bring a program to its knees. Several have lead me to successful DDoS or RCE. These occur in all languages, human error can easily and frequently be exploited.
Jan 26, 2017 at 20:58 comment added schroeder Ah, then what you are looking for are CVEs with exploits or PoCs.
Jan 26, 2017 at 20:53 comment added the_endian Kinda. I had a look at the site yesterday but there seems to be no real detail on how these things occur? In other words, it's very easy for me to understand a buffer overflow, format string, global address table, DDOS etc... in a technical sense. But the CVEs seem to just say "vulnerability which allowed xyz with no technical details.
Jan 26, 2017 at 20:48 comment added schroeder Not sure what you're asking, entirely. If you search for "Java CVE's" you will get a list of 475 vulnerabilities that have existed in Java alone (just things in the language) cvedetails.com/vulnerability-list/vendor_id-93/product_id-19117/… Is that the kind of thing you are looking for?
Jan 26, 2017 at 20:47 history edited schroeder CC BY-SA 3.0
deleted 79 characters in body
Jan 26, 2017 at 20:36 review First posts
Jan 26, 2017 at 20:42
Jan 26, 2017 at 20:35 history asked the_endian CC BY-SA 3.0