CVE-2024-33895: n/a
Source CVE Database V5
Not known to be exploited · CVSS 6.6 Medium · fixed in 21.2 : update affected systems when convenient.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 21.2
CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 2 Aug 2024
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 2026-10-25.
What to do
AI-suggested
1. Immediate firmware upgrade to versions 21.2s10 or 22.1s3 or later to ensure unique per-device encryption keys are used. 2. Implement strict network segmentation to isolate Cosy+ devices from general IT networks and limit access to trusted personnel and systems only. 3. Employ strong network access controls, including VPNs and multi-factor authentication, to reduce unauthorized access risk. 4. Regularly audit device configurations and monitor network traffic for unusual access patterns or attempts to retrieve configuration data. 5. Establish incident response procedures specific to industrial control system vulnerabilities, including rapid patch deployment and rollback plans. 6. Coordinate with device vendors for timely security updates and advisories. 7. Train operational technology (OT) staff on the importance of firmware updates and secure device management practices. 8. Consider deploying intrusion detection systems tailored for industrial protocols to detect exploitation attempts early.
Description
Cosy+ devices running a firmware 21.x below 21.2s10 or a firmware 22.x below 22.1s3 use a unique key to encrypt the configuration parameters. This is fixed in version 21.2s10 and 22.1s3, the key is now unique per device.
References
- ewon.biz/products/cosy/ewon-cosy-wifi (opens in a new tab)
- hms-networks.com/cyber-security (opens in a new tab)
- hmsnetworks.blob.core.windows.net/nlw/docs/default-source/products/cybersecurity/security-advisory/hms-security-advisory-2024-07-29-001--ewon-several-cosy--vulnerabilities.pdf (opens in a new tab)
- blog.syss.com/posts/hacking-a-secure-industrial-remote-access-gateway/ (opens in a new tab)
- seclists.org/fulldisclosure/2024/Aug/22 (opens in a new tab)