# CVE-2023-43771: Denial of service in n/a

> Crafted packets on the control port can crash the nqptp program, causing a denial of service for time synchronization services.

- **Severity:** Medium 5.5 (`CVSS:3.1/AC:L/AV:L/A:H/C:N/I:N/PR:L/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Sep 2023
- **Updated:** 25 Sep 2024
- **Also known as:** GHSA-gm5r-p3x6-43h6, openSUSE-SU-2024:14316-1

## What is CVE-2023-43771?

CVE-2023-43771 is a medium-severity denial of service vulnerability in n/a, published on 22 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In nqptp-message-handlers.c in nqptp before 1.2.3, crafted packets received on the control port could crash the program.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2023-43771?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nqptp` | openSUSE:Tumbleweed | All versions | 1.2.4-1.1 |

Products: Mikebrady Not Quite Ptp.

## How do I fix CVE-2023-43771?

Upgrade to a fixed version.

## Is CVE-2023-43771 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-43771 and fix it if it is affected.

What it is: CVE-2023-43771 is a medium-severity denial of service vulnerability in n/a, published on 22 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-43771 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-2023-43771/ (Markdown: https://insights.sbomify.com/CVE-2023-43771/index.md)
```

## Sources

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

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