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

> Attackers can bypass DEP and ASLR protections in AVG Internet Security 2015 due to predictable RWX memory allocations.

- **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:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Dec 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7j3c-xq3f-9cr8

## What is CVE-2015-8578?

CVE-2015-8578 is a medium-severity vulnerability in n/a, published on 16 Dec 2015. 

### Official description

AVG Internet Security 2015 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-8578?

It affects 1 product.


Products: Avg Internet Security.

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

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

## Is CVE-2015-8578 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-6510](https://insights.sbomify.com/CVE-2024-6510/): Local privilege escalation vulnerability in AVG Internet Security (high 7.8)
- [CVE-2014-9632](https://insights.sbomify.com/CVE-2014-9632/): Privilege escalation in n/a (high 7.2)
- [CVE-2010-5152](https://insights.sbomify.com/CVE-2010-5152/): Race condition in n/a (medium 6.2)

## Fix prompt for AI coding agents

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

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

## Sources

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

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