# CVE-2017-9811: Privilege escalation in n/a

> A local user can elevate privileges to root by abusing quarantine operations in the kav4fs-control binary of Kaspersky Anti-Virus for Linux File Server.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-c4hx-wh9v-47f2

## What is CVE-2017-9811?

CVE-2017-9811 is a critical vulnerability in n/a, published on 17 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The kluser is able to interact with the kav4fs-control binary in Kaspersky Anti-Virus for Linux File Server before Maintenance Pack 2 Critical Fix 4 (version 8.0.4.312). By abusing the quarantine read and write operations, it is possible to elevate the privileges to root.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2017-9811?

It affects 1 product.


Products: Kaspersky Anti-Virus for Linux Server.

## How do I fix CVE-2017-9811?

No fix has been published for CVE-2017-9811 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-9811 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-9811 exists.

Public exploit code:

- Kaspersky Anti-Virus File Server 8.0.3.297 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2017-9810](https://insights.sbomify.com/CVE-2017-9810/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2017-9812](https://insights.sbomify.com/CVE-2017-9812/): Path traversal in n/a (high 7.5)
- [CVE-2017-9813](https://insights.sbomify.com/CVE-2017-9813/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-9811 and fix it if it is affected.

What it is: CVE-2017-9811 is a critical vulnerability in n/a, published on 17 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-9811 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-9811/ (Markdown: https://insights.sbomify.com/CVE-2017-9811/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-9811
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-9811
- OSV: https://osv.dev/vulnerability/CVE-2017-9811

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-9811/
Summaries are generated and may contain mistakes; the official description above is the record.