7.2
CWE
427 94
Advisory Published
Updated

CVE-2017-6417: Code Injection

First published: Tue Mar 21 2017(Updated: )

Code injection vulnerability in Avira Total Security Suite 15.0 (and earlier), Optimization Suite 15.0 (and earlier), Internet Security Suite 15.0 (and earlier), and Free Security Suite 15.0 (and earlier) allows a local attacker to bypass a self-protection mechanism, inject arbitrary code, and take full control of any Avira process via a "DoubleAgent" attack. One perspective on this issue is that (1) these products do not use the Protected Processes feature, and therefore an attacker can enter an arbitrary Application Verifier Provider DLL under Image File Execution Options in the registry; (2) the self-protection mechanism is intended to block all local processes (regardless of privileges) from modifying Image File Execution Options for these products; and (3) this mechanism can be bypassed by an attacker who temporarily renames Image File Execution Options during the attack.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
Avira Free Security Suite<=15.0
Avira Internet Security Suite<=15.0
Avira Optimization Suite<=15.0
Avira Total Security Suite<=15.0

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2017-6417?

    CVE-2017-6417 is considered to have a critical severity due to its potential to allow local attackers to execute arbitrary code.

  • How do I fix CVE-2017-6417?

    To fix CVE-2017-6417, users should upgrade to versions of the affected Avira products released after 15.0, which address this vulnerability.

  • Who is affected by CVE-2017-6417?

    CVE-2017-6417 affects users of Avira Free Security Suite, Internet Security Suite, Optimization Suite, and Total Security Suite, all versions 15.0 and earlier.

  • What types of attacks can exploit CVE-2017-6417?

    CVE-2017-6417 can be exploited by local attackers to bypass the self-protection mechanism of the software and inject arbitrary code.

  • Is there a workaround for CVE-2017-6417?

    There are currently no known workarounds for CVE-2017-6417 other than upgrading to an unaffected version.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203