What is the severity of CVE-2017-9810?

CVE-2017-9810 is classified as a high-severity vulnerability due to the potential for unauthorized actions on behalf of authenticated users.

How do I fix CVE-2017-9810?

To fix CVE-2017-9810, upgrade to Kaspersky Anti-Virus for Linux File Server version 8.0.4.312 or later, which includes Anti-CSRF tokens in forms.

What types of attacks can exploit CVE-2017-9810?

CVE-2017-9810 can be exploited through Cross-Site Request Forgery (CSRF) attacks, allowing unauthorized requests to be sent by an attacker.

Which versions of Kaspersky Anti-Virus are affected by CVE-2017-9810?

CVE-2017-9810 affects Kaspersky Anti-Virus for Linux File Server versions up to and including 8.0.3.297.

Is there a workaround for CVE-2017-9810?

There is no official workaround for CVE-2017-9810; the recommended solution is to update to a fixed version.

Vulnerability/
CVE-2017-9810

high

8.8

CWE

352

17/7/2017

5/8/2024

CVE-2017-9810: CSRF

First published: Mon Jul 17 2017(Updated: )

There are no Anti-CSRF tokens in any forms on the web interface in Kaspersky Anti-Virus for Linux File Server before Maintenance Pack 2 Critical Fix 4 (version 8.0.4.312). This would allow an attacker to submit authenticated requests when an authenticated user browses an attacker-controlled domain.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Kaspersky Anti-virus For Linux Server	<=8.0.3.297

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-9810?
CVE-2017-9810 is classified as a high-severity vulnerability due to the potential for unauthorized actions on behalf of authenticated users.
How do I fix CVE-2017-9810?
To fix CVE-2017-9810, upgrade to Kaspersky Anti-Virus for Linux File Server version 8.0.4.312 or later, which includes Anti-CSRF tokens in forms.
What types of attacks can exploit CVE-2017-9810?
CVE-2017-9810 can be exploited through Cross-Site Request Forgery (CSRF) attacks, allowing unauthorized requests to be sent by an attacker.
Which versions of Kaspersky Anti-Virus are affected by CVE-2017-9810?
CVE-2017-9810 affects Kaspersky Anti-Virus for Linux File Server versions up to and including 8.0.3.297.
Is there a workaround for CVE-2017-9810?
There is no official workaround for CVE-2017-9810; the recommended solution is to update to a fixed version.

collector/nvd-index
agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/author
agent/weakness
agent/last-modified-date
agent/tags
agent/first-publish-date
agent/event
agent/description
agent/source
vendor/kaspersky
canonical/kaspersky anti-virus for linux server
version/kaspersky anti-virus for linux server/8.0.3.297

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-9810?
CVE-2017-9810 is classified as a high-severity vulnerability due to the potential for unauthorized actions on behalf of authenticated users.
How do I fix CVE-2017-9810?
To fix CVE-2017-9810, upgrade to Kaspersky Anti-Virus for Linux File Server version 8.0.4.312 or later, which includes Anti-CSRF tokens in forms.
What types of attacks can exploit CVE-2017-9810?
CVE-2017-9810 can be exploited through Cross-Site Request Forgery (CSRF) attacks, allowing unauthorized requests to be sent by an attacker.
Which versions of Kaspersky Anti-Virus are affected by CVE-2017-9810?
CVE-2017-9810 affects Kaspersky Anti-Virus for Linux File Server versions up to and including 8.0.3.297.
Is there a workaround for CVE-2017-9810?
There is no official workaround for CVE-2017-9810; the recommended solution is to update to a fixed version.