CVE-2024-32384: Kerlink gateways · Cleartext Transmission
Source CVE Database V5
Not known to be exploited · CVSS 6.8 Medium · fixed in 5.10 : update affected systems when convenient.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.10
CVSS:3.1/AC:H/AV:N/A:N/C:H/I:H/PR:N/S:U/UI:RExploitation evidence
Disclosed: evidence found.
CVE published 1 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
- Upgrade all Kerlink gateways to KerOS version 5.10 or later to ensure HTTPS support and encrypted management interfaces.
- Implement strict network segmentation to isolate management interfaces from general user networks and the internet.
- Use VPNs or secure tunnels (e.g., SSH tunnels) to access the web interface remotely, preventing exposure over untrusted networks.
- Enforce strong authentication mechanisms and monitor access logs for unusual activity.
- Deploy network intrusion detection systems (NIDS) to detect potential man-in-the-middle or traffic manipulation attempts.
- Educate administrators on the risks of accessing device interfaces over unsecured networks and encourage the use of secure channels.
- Regularly audit device configurations and firmware versions to ensure compliance with security policies.
- If upgrading is not immediately possible, consider disabling web interface access or restricting it to trusted IP addresses only.
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.