# OSV-2020-305: Stack-buffer-overflow in ot::NetworkData::Leader::SendCommissioningGetResponse

> A stack buffer overflow in OpenThread's NetworkData Leader allows remote attackers to cause denial of service or potentially execute code via crafted CoAP messages.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jun 2020

## What is OSV-2020-305?

OSV-2020-305 is a memory corruption vulnerability in openthread, published on 30 Jun 2020. It can be exploited over the network, with no action from the victim.

### Official description

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=17297

```
Crash type: Stack-buffer-overflow READ 1
Crash state:
ot::NetworkData::Leader::SendCommissioningGetResponse
ot::NetworkData::Leader::HandleCommissioningGet
ot::Coap::CoapBase::ProcessReceivedRequest
```

## Which versions are affected by OSV-2020-305?

1 open source package ship an affected version, including openthread.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openthread` | OSS-Fuzz | All versions | None |

## How do I fix OSV-2020-305?

No fix has been published for OSV-2020-305 yet. Limit exposure of the affected software until one is available.

## Is OSV-2020-305 being exploited?

There is no known exploitation of OSV-2020-305 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2020-305 and fix it if it is affected.

What it is: OSV-2020-305 is a memory corruption vulnerability in openthread, published on 30 Jun 2020. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of OSV-2020-305 in the wild and no public exploit code.

Affected packages and fixed versions:
- openthread (OSS-Fuzz): affected all versions; no fix listed

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/OSV-2020-305/ (Markdown: https://insights.sbomify.com/OSV-2020-305/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2020-305

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