An unauthenticated attacker could leverage this vulnerability to achieve arbitrary code execution in the context of the current user. We will continue to watch this closely.Accellion FTA OS Command Injection VulnerabilityĪccellion FTA 9_12_370 and earlier is affected by OS command execution via a crafted POST request to various admin endpoints.Īccellion FTA 9_12_411 and earlier is affected by OS command execution via a local web service call.Īccellion FTA SQL Injection VulnerabilityĪccellion FTA 9_12_370 and earlier is affected by SQL injection via a crafted Host header in a request to document_root.html.Īccellion FTA 9_12_411 and earlier is affected by SSRF via a crafted POST request to wmProgressstat.html.Īdobe Acrobat and Reader Heap-based Buffer Overflow VulnerabilityĪcrobat Reader DC versions versions 2020.013.20074 (and earlier), 2020.001.30018 (and earlier) and 2017.011.30188 (and earlier) are affected by a heap-based buffer overflow vulnerability. We've found that many customers are starting to look for PDF alternatives to use in their environment. The attached article explains how to opt-out of this, but our concern is in the future, this may be a requirement and not an option. In addition to the change, Adobe now requires users who install Adobe Reader 64-bit to create an individual account and login each time they use the software. More information on this can be found in Adobe's Adobe - 64-bit Unified App Installer article. This also affects PDQ Inventory collections as well. The 64-bit version of Adobe Reader that Adobe provides actually installs Adobe Acrobat (according to the registry and appwiz.cpl) and not Adobe Reader, which makes tracking 'Free' vs 'Paid' installations of Adobe Acrobat/Adobe Reader (64-bit) incredibly difficult. Our packaging team has been evaluating a 64-bit Adobe Reader package, though there are issues that may prevent this from being possible.

Latest version of adobe reader msi