# CVE-2015-0744: Denial of service in n/a

> Remote attackers can cause denial of service in Cisco DTACS via TCP traffic floods, impacting system availability.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 May 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-jh7c-62vv-m75j

## What is CVE-2015-0744?

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

### Official description

Cisco DTA Control System (DTACS) 4.0.0.9 and Cisco Headend System Release allow remote attackers to cause a denial of service (CPU and memory consumption, and TCP service outage) via (1) a SYN flood or (2) another type of TCP traffic flood, aka Bug IDs CSCus50642, CSCus50662, CSCus50625, CSCus50657, and CSCus68315.

Weakness: CWE-399

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

It affects 3 products.


Products: Cisco Dta Control System, Cisco Headend Digital Broadband Delivery System, Cisco Headend System Release.

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

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

## Is CVE-2015-0744 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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