# CVE-2024-32384: Other in n/a

> Kerlink gateways lack HTTPS support, allowing man-in-the-middle attackers to intercept and modify web interface traffic.

- **Severity:** Medium 6.8 (`CVSS:3.1/AC:H/AV:N/A:N/C:H/I:H/PR:N/S:U/UI:R`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Dec 2025
- **Updated:** 1 Dec 2025
- **Also known as:** GHSA-g66h-9qrm-pfwx

## What is CVE-2024-32384?

CVE-2024-32384 is a medium-severity vulnerability in n/a, published on 1 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Kerlink gateways running KerOS prior to version 5.10 expose their web interface exclusively over HTTP, without HTTPS support. This lack of transport layer security allows a man-in-the-middle attacker to intercept and modify traffic between the client and the device.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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

It affects 1 product.


Products: Kerlink Keros.

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

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

## Is CVE-2024-32384 being exploited?

There is no known exploitation of CVE-2024-32384 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-32388](https://insights.sbomify.com/CVE-2024-32388/): Misconfiguration in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-32384 is a medium-severity vulnerability in n/a, published on 1 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-32384 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-32384/ (Markdown: https://insights.sbomify.com/CVE-2024-32384/index.md)
```

## Sources

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

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