# CVE-2015-8579: Security feature bypass in n/a

> Attackers can bypass DEP and ASLR protections in Kaspersky Total Security due to predictable RWX memory allocations, facilitating further exploitation.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Dec 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-97gf-xj33-q8p2

## What is CVE-2015-8579?

CVE-2015-8579 is a medium-severity vulnerability in n/a, published on 16 Dec 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Kaspersky Total Security 2015 15.0.2.361 allocates memory with Read, Write, Execute (RWX) permissions at predictable addresses when protecting user-mode processes, which allows attackers to bypass the DEP and ASLR protection mechanisms via unspecified vectors.

Weakness: CWE-264

## Which versions are affected by CVE-2015-8579?

It affects 1 product.


Products: Kaspersky Total Security 2015.

## How do I fix CVE-2015-8579?

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

## Is CVE-2015-8579 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-8579 and fix it if it is affected.

What it is: CVE-2015-8579 is a medium-severity vulnerability in n/a, published on 16 Dec 2015. 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-2015-8579 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-2015-8579/ (Markdown: https://insights.sbomify.com/CVE-2015-8579/index.md)
```

## Sources

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

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