# CVE-2022-29767: Denial of service in n/a

> Attackers can cause a Denial of Service via high CPU usage by establishing a large number of connections to the adbyby proxy service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-jfpm-rpx4-72wc

## What is CVE-2022-29767?

CVE-2022-29767 is a medium-severity denial of service vulnerability in n/a, published on 3 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

adbyby v2.7 allows external users to make connections via port 8118. This can cause a program logic error and lead to a Denial of Service (DoS) via high CPU usage due to a large number of connections.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

It affects 1 product.


Products: Adbyby Project Adbyby.

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

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

## Is CVE-2022-29767 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-29767 is a medium-severity denial of service vulnerability in n/a, published on 3 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-29767 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-2022-29767/ (Markdown: https://insights.sbomify.com/CVE-2022-29767/index.md)
```

## Sources

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

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