# CVE-2022-47517: Memory corruption in n/a

> Remote attackers can crash the drachtio-server daemon via a crafted UDP message causing a heap-based buffer over-read.

- **Severity:** High 7.5 (`CVSS:3.1/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:** 18 Dec 2022
- **Updated:** 17 Apr 2025
- **Also known as:** GHSA-c8mq-83h4-gm57

## What is CVE-2022-47517?

CVE-2022-47517 is a high-severity memory corruption vulnerability in n/a, published on 18 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in the libsofia-sip fork in drachtio-server before 0.8.19. It allows remote attackers to cause a denial of service (daemon crash) via a crafted UDP message that causes a url_canonize2 heap-based buffer over-read because of an off-by-one error.

Weakness: CWE-193 (Off-by-one Error)

## Which versions are affected by CVE-2022-47517?

It affects 1 product.


Products: Drachtio Drachtio-Server.

## How do I fix CVE-2022-47517?

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

## Is CVE-2022-47517 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-47517 exists.

## Other vulnerabilities in n/a

- [CVE-2022-45474](https://insights.sbomify.com/CVE-2022-45474/): Use after free in n/a (critical 9.8)
- [CVE-2022-45909](https://insights.sbomify.com/CVE-2022-45909/): Memory corruption in n/a (critical 9.1)
- [CVE-2022-47515](https://insights.sbomify.com/CVE-2022-47515/): Denial of service in n/a (high 7.5)
- [CVE-2022-47516](https://insights.sbomify.com/CVE-2022-47516/): Denial of service in n/a (high 7.5)
- [CVE-2022-45473](https://insights.sbomify.com/CVE-2022-45473/): Misconfiguration in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-47517 and fix it if it is affected.

What it is: CVE-2022-47517 is a high-severity memory corruption vulnerability in n/a, published on 18 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-47517 exists.

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-2022-47517/ (Markdown: https://insights.sbomify.com/CVE-2022-47517/index.md)
```

## Sources

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

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