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

> A remote attacker can cause a denial-of-service in Fox-IT DataDiode via a divide-by-zero error in the packet parser.

- **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:** 30 May 2023
- **Updated:** 14 Jan 2025
- **Also known as:** GHSA-j49c-jwhf-pgwq

## What is CVE-2022-47525?

CVE-2022-47525 is a high-severity denial of service vulnerability in n/a, published on 30 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Fox-IT DataDiode (aka Fox DataDiode) 3.4.3 suffers from a Divide-by-Zero vulnerability in the packet parser. A remote attacker could leverage this vulnerability to cause a denial-of-service. Exploitation of this issue does not require user interaction.

Weakness: CWE-369 (Divide By Zero)

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

It affects 1 product.


Products: Fox-It Fox Datadiode Firmware.

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

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

## Is CVE-2022-47525 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-47526](https://insights.sbomify.com/CVE-2022-47526/): Path traversal in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-47525 is a high-severity denial of service vulnerability in n/a, published on 30 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-47525 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-47525/ (Markdown: https://insights.sbomify.com/CVE-2022-47525/index.md)
```

## Sources

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

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