File _patchinfo of Package patchinfo.2861
<patchinfo incident="2861"> <packager>AndreasStieger</packager> <issue tracker="cve" id="2016-4172"></issue> <issue tracker="cve" id="2016-4173"></issue> <issue tracker="cve" id="2016-4174"></issue> <issue tracker="cve" id="2016-4175"></issue> <issue tracker="cve" id="2016-4176"></issue> <issue tracker="cve" id="2016-4177"></issue> <issue tracker="cve" id="2016-4178"></issue> <issue tracker="cve" id="2016-4179"></issue> <issue tracker="cve" id="2016-4180"></issue> <issue tracker="cve" id="2016-4181"></issue> <issue tracker="cve" id="2016-4182"></issue> <issue tracker="cve" id="2016-4183"></issue> <issue tracker="cve" id="2016-4184"></issue> <issue tracker="cve" id="2016-4185"></issue> <issue tracker="cve" id="2016-4186"></issue> <issue tracker="cve" id="2016-4187"></issue> <issue tracker="cve" id="2016-4188"></issue> <issue tracker="cve" id="2016-4189"></issue> <issue tracker="cve" id="2016-4190"></issue> <issue tracker="cve" id="2016-4217"></issue> <issue tracker="cve" id="2016-4218"></issue> <issue tracker="cve" id="2016-4219"></issue> <issue tracker="cve" id="2016-4220"></issue> <issue tracker="cve" id="2016-4221"></issue> <issue tracker="cve" id="2016-4222"></issue> <issue tracker="cve" id="2016-4223"></issue> <issue tracker="cve" id="2016-4224"></issue> <issue tracker="cve" id="2016-4225"></issue> <issue tracker="cve" id="2016-4226"></issue> <issue tracker="cve" id="2016-4227"></issue> <issue tracker="cve" id="2016-4228"></issue> <issue tracker="cve" id="2016-4229"></issue> <issue tracker="cve" id="2016-4230"></issue> <issue tracker="cve" id="2016-4231"></issue> <issue tracker="cve" id="2016-4232"></issue> <issue tracker="cve" id="2016-4233"></issue> <issue tracker="cve" id="2016-4234"></issue> <issue tracker="cve" id="2016-4235"></issue> <issue tracker="cve" id="2016-4236"></issue> <issue tracker="cve" id="2016-4237"></issue> <issue tracker="cve" id="2016-4238"></issue> <issue tracker="cve" id="2016-4239"></issue> <issue tracker="cve" id="2016-4240"></issue> <issue tracker="cve" id="2016-4241"></issue> <issue tracker="cve" id="2016-4242"></issue> <issue tracker="cve" id="2016-4243"></issue> <issue tracker="cve" id="2016-4244"></issue> <issue tracker="cve" id="2016-4245"></issue> <issue tracker="cve" id="2016-4246"></issue> <issue tracker="cve" id="2016-4247"></issue> <issue tracker="cve" id="2016-4248"></issue> <issue tracker="cve" id="2016-4249"></issue> <issue tracker="bnc" id="988579">VUL-0: flash-player: version update 11.2.202.632</issue> <category>security</category> <rating>important</rating> <summary>Security update for flash-player</summary> <description>Adobe Flash Player was updated to 11.2.202.632 to fix many security issues tracked under the upstream advisory APSB16-25, allowing remote attackers to execute arbitrary code when delivering specially crafted Flash content. The following vulnerabilities were fixed: - CVE-2016-4172: memory corruption vulnerability that could lead to code execution - CVE-2016-4173: use-after-free vulnerability that could lead to code execution - CVE-2016-4174: use-after-free vulnerability that could lead to code execution - CVE-2016-4175: memory corruption vulnerability that could lead to code execution - CVE-2016-4176: stack corruption vulnerability that could lead to code execution - CVE-2016-4177: stack corruption vulnerability that could lead to code execution - CVE-2016-4178: security bypass vulnerability that could lead to information disclosure - CVE-2016-4179: memory corruption vulnerability that could lead to code execution - CVE-2016-4180: memory corruption vulnerability that could lead to code execution - CVE-2016-4181: memory corruption vulnerability that could lead to code execution - CVE-2016-4182: memory corruption vulnerability that could lead to code execution - CVE-2016-4183: memory corruption vulnerability that could lead to code execution - CVE-2016-4184: memory corruption vulnerability that could lead to code execution - CVE-2016-4185: memory corruption vulnerability that could lead to code execution - CVE-2016-4186: memory corruption vulnerability that could lead to code execution - CVE-2016-4187: memory corruption vulnerability that could lead to code execution - CVE-2016-4188: memory corruption vulnerability that could lead to code execution - CVE-2016-4189: memory corruption vulnerability that could lead to code execution - CVE-2016-4190: memory corruption vulnerability that could lead to code execution - CVE-2016-4217: memory corruption vulnerability that could lead to code execution - CVE-2016-4218: memory corruption vulnerability that could lead to code execution - CVE-2016-4219: memory corruption vulnerability that could lead to code execution - CVE-2016-4220: memory corruption vulnerability that could lead to code execution - CVE-2016-4221: memory corruption vulnerability that could lead to code execution - CVE-2016-4222: use-after-free vulnerability that could lead to code execution - CVE-2016-4223: type confusion vulnerability that could lead to code execution - CVE-2016-4224: type confusion vulnerability that could lead to code execution - CVE-2016-4225: type confusion vulnerability that could lead to code execution - CVE-2016-4226: use-after-free vulnerability that could lead to code execution - CVE-2016-4227: use-after-free vulnerability that could lead to code execution - CVE-2016-4228: use-after-free vulnerability that could lead to code execution - CVE-2016-4229: use-after-free vulnerability that could lead to code execution - CVE-2016-4230: use-after-free vulnerability that could lead to code execution - CVE-2016-4231: use-after-free vulnerability that could lead to code execution - CVE-2016-4232: memory leak vulnerability - CVE-2016-4233: memory corruption vulnerability that could lead to code execution - CVE-2016-4234: memory corruption vulnerability that could lead to code execution - CVE-2016-4235: memory corruption vulnerability that could lead to code execution - CVE-2016-4236: memory corruption vulnerability that could lead to code execution - CVE-2016-4237: memory corruption vulnerability that could lead to code execution - CVE-2016-4238: memory corruption vulnerability that could lead to code execution - CVE-2016-4239: memory corruption vulnerability that could lead to code execution - CVE-2016-4240: memory corruption vulnerability that could lead to code execution - CVE-2016-4241: memory corruption vulnerability that could lead to code execution - CVE-2016-4242: memory corruption vulnerability that could lead to code execution - CVE-2016-4243: memory corruption vulnerability that could lead to code execution - CVE-2016-4244: memory corruption vulnerability that could lead to code execution - CVE-2016-4245: memory corruption vulnerability that could lead to code execution - CVE-2016-4246: memory corruption vulnerability that could lead to code execution - CVE-2016-4247: race condition vulnerability that could lead to information disclosure - CVE-2016-4248: use-after-free vulnerability that could lead to code execution - CVE-2016-4249: heap buffer overflow vulnerability that could lead to code execution</description> </patchinfo>
