What is the severity of CVE-2017-8307?

CVE-2017-8307 has a high severity rating due to its potential for unauthorized file manipulation by unprivileged users.

How do I fix CVE-2017-8307?

To mitigate CVE-2017-8307, ensure that Avast Self-Defense is enabled and consider updating to a version later than 12.3.2279.

What products are affected by CVE-2017-8307?

CVE-2017-8307 affects Avast Antivirus versions prior to v17.

Can CVE-2017-8307 be exploited remotely?

CVE-2017-8307 requires local access, as it can only be exploited by unprivileged users on systems where Avast Self-Defense is disabled.

What type of vulnerability is CVE-2017-8307?

CVE-2017-8307 is a file manipulation vulnerability that allows unauthorized access to files via the LPC interface API.

Vulnerability/
CVE-2017-8307

critical

9.8

27/4/2017

5/8/2024

CVE-2017-8307

First published: Thu Apr 27 2017(Updated: )

In Avast Antivirus before v17, using the LPC interface API exposed by the AvastSVC.exe Windows service, it is possible to launch predefined binaries, or replace or delete arbitrary files. This vulnerability is exploitable by any unprivileged user when Avast Self-Defense is disabled. It is also exploitable in conjunction with CVE-2017-8308 when Avast Self-Defense is enabled. The vulnerability allows for Denial of Service attacks and hiding traces of a possible attack.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Avast Antivirus	<=12.3.2279

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-8307?
CVE-2017-8307 has a high severity rating due to its potential for unauthorized file manipulation by unprivileged users.
How do I fix CVE-2017-8307?
To mitigate CVE-2017-8307, ensure that Avast Self-Defense is enabled and consider updating to a version later than 12.3.2279.
What products are affected by CVE-2017-8307?
CVE-2017-8307 affects Avast Antivirus versions prior to v17.
Can CVE-2017-8307 be exploited remotely?
CVE-2017-8307 requires local access, as it can only be exploited by unprivileged users on systems where Avast Self-Defense is disabled.
What type of vulnerability is CVE-2017-8307?
CVE-2017-8307 is a file manipulation vulnerability that allows unauthorized access to files via the LPC interface API.

agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/author
agent/severity
agent/last-modified-date
agent/description
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/avast
canonical/avast antivirus
version/avast antivirus/12.3.2279

Company

Resources

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.

Frequently Asked Questions

What is the severity of CVE-2017-8307?
CVE-2017-8307 has a high severity rating due to its potential for unauthorized file manipulation by unprivileged users.
How do I fix CVE-2017-8307?
To mitigate CVE-2017-8307, ensure that Avast Self-Defense is enabled and consider updating to a version later than 12.3.2279.
What products are affected by CVE-2017-8307?
CVE-2017-8307 affects Avast Antivirus versions prior to v17.
Can CVE-2017-8307 be exploited remotely?
CVE-2017-8307 requires local access, as it can only be exploited by unprivileged users on systems where Avast Self-Defense is disabled.
What type of vulnerability is CVE-2017-8307?
CVE-2017-8307 is a file manipulation vulnerability that allows unauthorized access to files via the LPC interface API.