52 multiplatform vulnerabilities
- Home
- Board: /g/ - Technology
- Reading: 52 multiplatform vulnerabilities
https://helpx.adobe.com/security/products/flash-player/apsb16-25.html#table
>Platform: Windows, Macintosh, Linux and ChromeOS
>These updates resolve a race condition vulnerability that could lead to information disclosure (CVE-2016-4247).
>These updates resolve type confusion vulnerabilities that could lead to code execution (CVE-2016-4223, CVE-2016-4224, CVE-2016-4225).
>These updates resolve use-after-free vulnerabilities that could lead to code execution (CVE-2016-4173, CVE-2016-4174, CVE-2016-4222, CVE-2016-4226, CVE-2016-4227, CVE-2016-4228, CVE-2016-4229, CVE-2016-4230, CVE-2016-4231, CVE-2016-4248).
>These updates resolve a heap buffer overflow vulnerability that could lead to code execution (CVE-2016-4249).
>These updates resolve memory corruption vulnerabilities that could lead to code execution (CVE-2016-4172, CVE-2016-4175, CVE-2016-4179, CVE-2016-4180, CVE-2016-4181, CVE-2016-4182, CVE-2016-4183, CVE-2016-4184, CVE-2016-4185, CVE-2016-4186, CVE-2016-4187, CVE-2016-4188, CVE-2016-4189, CVE-2016-4190, CVE-2016-4217, CVE-2016-4218, CVE-2016-4219, CVE-2016-4220, CVE-2016-4221, CVE-2016-4233, CVE-2016-4234, CVE-2016-4235, CVE-2016-4236, CVE-2016-4237, CVE-2016-4238, CVE-2016-4239, CVE-2016-4240, CVE-2016-4241, CVE-2016-4242, CVE-2016-4243, CVE-2016-4244, CVE-2016-4245, CVE-2016-4246).
>These updates resolve a memory leak vulnerability (CVE-2016-4232).
>These updates resolve stack corruption vulnerabilities that could lead to code execution (CVE-2016-4176, CVE-2016-4177).
>These updates resolve a security bypass vulnerability that could lead to information disclosure (CVE-2016-4178)
>>55580908
>Adobe
This is why you need to extinguish hindus and their technology
>>55580908
>oh look. it say "vulnerability". i need to spam it everywhere
do you even know what they are referring to. if you don't then you're an idiot for posting that.
>use after free
>heap buffer overflow
>memory corruption
See, C is unsafe as fuck.
>>55581011
https://cve.mitre.org/about/terminology.html
I understand you probably meant they are alone not exploits, but if you don't find this situation grave you should revise your standards.
>>55581044
How are you sure this was written in C? For all we know it might even have been plain assembly.
Also, it is not like managed languages are fail proof.
>>55581159
Pretty sure that Flash is not written in any assembly.
They don't have issues with them that are this bad.
>>55581175
Well, surely not in full, but I would be surprised if there are not some parts of it that are.
>>55581044
i can "recreate" all of that in any non-memory managed language
>inb4 i can crash a car by """forgetting""" to break on curves
>>55581251
Ok, show me an example of use after free in python.
>>55581274
ill do you one better, ill fuck your ints
>>55581385
Of course, IntStruct.from_address is a method you would accidentally use in your code.
>>55581405
really nigga? is that your reply to
>i can crash stuff if i want to
>except in python
>yea i can
?
you do know static code analysis tools exist right? cmon...
Kinda weird how they find half a dozen new vulnerabilities per week, every week for several years.
>>55581274
No serious programmer uses Python though
