# CVE-2015-8299: Memory corruption in n/a

> Remote attackers can execute arbitrary code via crafted UDP packets due to a buffer overflow in the KNX ETS Group messages monitor.

- **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:** 29 Aug 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6gcm-p4rc-j4j6

## What is CVE-2015-8299?

CVE-2015-8299 is a critical memory corruption vulnerability in n/a, published on 29 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in the Group messages monitor (Falcon) in KNX ETS 4.1.5 (Build 3246) allows remote attackers to execute arbitrary code via a crafted KNXnet/IP UDP packet.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Knx Ets.

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

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

## Is CVE-2015-8299 being exploited?

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

Public exploit code:

- CVE-2015-8299 Advisory and PoC (github_poc): https://github.com/kernoelpanic/CVE-2015-8299

## Fix prompt for AI coding agents

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

What it is: CVE-2015-8299 is a critical memory corruption vulnerability in n/a, published on 29 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-8299 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-8299/ (Markdown: https://insights.sbomify.com/CVE-2015-8299/index.md)
```

## Sources

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

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