# CVE-2024-32388: Misconfiguration in n/a

> Attackers can bypass firewall restrictions on Kerlink devices to access protected UDP services due to incorrect configuration.

- **Severity:** Medium 5.3 (`CVSS:3.1/AC:L/AV:N/A:N/C:L/I:N/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Dec 2025
- **Updated:** 1 Dec 2025
- **Also known as:** GHSA-fh4c-98rx-vxvw

## What is CVE-2024-32388?

CVE-2024-32388 is a medium-severity vulnerability in n/a, published on 1 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Due to a firewall misconfiguration, Kerlink devices running KerOS prior to 5.12 incorrectly accept specially crafted UDP packets. This allows an attacker to bypass the firewall and access UDP-based services that would otherwise be protected.

Weakness: CWE-940 (Improper Verification of Source of a Communication Channel), CWE-402 (Transmission of Private Resources into a New Sphere)

## Which versions are affected by CVE-2024-32388?

It affects 1 product.


Products: Kerlink Keros.

## How do I fix CVE-2024-32388?

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

## Is CVE-2024-32388 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-39148](https://insights.sbomify.com/CVE-2024-39148/): Command injection in n/a (high 8.1)
- [CVE-2024-32384](https://insights.sbomify.com/CVE-2024-32384/): Other in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-32388 and fix it if it is affected.

What it is: CVE-2024-32388 is a medium-severity vulnerability in n/a, published on 1 Dec 2025. 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-2024-32388 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-2024-32388/ (Markdown: https://insights.sbomify.com/CVE-2024-32388/index.md)
```

## Sources

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

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