Adobe Flash Player before 188.8.131.52 and 14.x and 15.x before 184.108.40.206 on Windows and OS X and before 220.127.116.111 on Linux, Adobe AIR before 18.104.22.1683, Adobe AIR SDK before 22.214.171.1242, and Adobe AIR SDK & Compiler before 126.96.36.1992 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2014-0564.
The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
|Name||Vendor||Start Version||End Version|
|Red Hat Enterprise Linux 5 Supplementary||RedHat||flash-plugin-0:188.8.131.521-1.el5||*|
|Supplementary for Red Hat Enterprise Linux 6||RedHat||flash-plugin-0:184.108.40.2061-1.el6||*|
When a product allows a user’s input to contain code syntax, it might be possible for an attacker to craft the code in such a way that it will alter the intended control flow of the product. Such an alteration could lead to arbitrary code execution. Injection problems encompass a wide variety of issues – all mitigated in very different ways. For this reason, the most effective way to discuss these weaknesses is to note the distinct features which classify them as injection weaknesses. The most important issue to note is that all injection problems share one thing in common – i.e., they allow for the injection of control plane data into the user-controlled data plane. This means that the execution of the process may be altered by sending code in through legitimate data channels, using no other mechanism. While buffer overflows, and many other flaws, involve the use of some further issue to gain execution, injection problems need only for the data to be parsed. The most classic instantiations of this category of weakness are SQL injection and format string vulnerabilities.