# CVE-2019-9582: Denial of service in n/a

> Outdated base software in eQ-3 Homematic CCU2 devices allows attackers to cause a denial of service.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 14 Aug 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-p97m-jc8r-p95p

## What is CVE-2019-9582?

CVE-2019-9582 is a high-severity denial of service vulnerability in n/a, published on 14 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

eQ-3 Homematic CCU2 outdated base software packages allows Denial of Service. CCU2 affected versions: 2.35.16, 2.41.5, 2.41.8, 2.41.9, 2.45.6, 2.45.7, 2.47.10, 2.47.12, 2.47.15.

## Which versions are affected by CVE-2019-9582?

It affects 1 product.


Products: Eq-3 Homematic Ccu2 Firmware.

## How do I fix CVE-2019-9582?

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

## Is CVE-2019-9582 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-33032](https://insights.sbomify.com/CVE-2021-33032/): Command injection in n/a (critical 10.0)
- [CVE-2019-18937](https://insights.sbomify.com/CVE-2019-18937/): Command injection in n/a (critical 9.8)
- [CVE-2019-18938](https://insights.sbomify.com/CVE-2019-18938/): Code injection in n/a (critical 9.8)
- [CVE-2019-18939](https://insights.sbomify.com/CVE-2019-18939/): Command injection in n/a (critical 9.8)
- [CVE-2019-16199](https://insights.sbomify.com/CVE-2019-16199/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-9582 and fix it if it is affected.

What it is: CVE-2019-9582 is a high-severity denial of service vulnerability in n/a, published on 14 Aug 2019. 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-2019-9582 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-2019-9582/ (Markdown: https://insights.sbomify.com/CVE-2019-9582/index.md)
```

## Sources

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

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