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

> Remote attackers can jam key fob requests via RF, causing denial of service for Joy ebike Wolf Manufacturing users.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-6rcj-vxjg-f6mw

## What is CVE-2022-30467?

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

### Official description

Joy ebike Wolf Manufacturing year 2022 is vulnerable to Denial of service, which allows remote attackers to jam the key fob request via RF.

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

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

It affects 1 product.


Products: Joyebike Wolf 2022 Firmware.

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

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

## Is CVE-2022-30467 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-30467 is a medium-severity denial of service vulnerability in n/a, published on 29 Jun 2022. 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-2022-30467 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-30467/ (Markdown: https://insights.sbomify.com/CVE-2022-30467/index.md)
```

## Sources

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

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