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

> Attackers can launch Distributed Denial of Service attacks against IoTivity CoAP servers via UDP amplification using spoofed IP addresses.

- **Severity:** Critical 9.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:** 13 Mar 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-8vwf-phwx-jwqp

## What is CVE-2019-9750?

CVE-2019-9750 is a critical denial of service vulnerability in n/a, published on 13 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In IoTivity through 1.3.1, the CoAP server interface can be used for Distributed Denial of Service attacks using source IP address spoofing and UDP-based traffic amplification. The reflected traffic is 6 times bigger than spoofed requests. This occurs because the construction of a "4.01 Unauthorized" response is mishandled. NOTE: the vendor states "While this is an interesting attack, there is no plan for maintainer to fix, as we are migrating to IoTivity Lite."

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 1 product.


Products: Iotivity Iotivity.

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

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

## Is CVE-2019-9750 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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