# CVE-2018-7535: Privilege escalation in n/a

> Local attackers can escalate privileges or gain full control by exploiting weak file permissions in the TotalAV installation directory.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-wr54-8xf4-92p3

## What is CVE-2018-7535?

CVE-2018-7535 is a high-severity vulnerability in n/a, published on 13 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in TotalAV v4.1.7. An unprivileged user could modify or overwrite all of the product's files because of weak permissions (Everyone:F) under %PROGRAMFILES%, which allows local users to gain privileges or obtain maximum control over the product.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2018-7535?

It affects 1 product.


Products: Totalav Totalav.

## How do I fix CVE-2018-7535?

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

## Is CVE-2018-7535 being exploited?

There is no known exploitation of CVE-2018-7535 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2021-47787](https://insights.sbomify.com/CVE-2021-47787/): TotalAV 5.15.69 - Unquoted Service Path (high 8.5)
- [CVE-2024-31771](https://insights.sbomify.com/CVE-2024-31771/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-7535 and fix it if it is affected.

What it is: CVE-2018-7535 is a high-severity vulnerability in n/a, published on 13 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-7535 in the wild and no public exploit code.

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-2018-7535/ (Markdown: https://insights.sbomify.com/CVE-2018-7535/index.md)
```

## Sources

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

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