CVE-2024-33896: Cosy+ devices · OS Command Injection
Source CVE Database V5
Public exploit available (Exploit-DB) · CVSS 7.2 High · fixed in 21.2 : patch affected systems as a priority.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 4.0% chance of exploitation in 30 days – higher than 90% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 21.2
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 2 Aug 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
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
Timeline
CVE ID reserved
by MITRE Corporation
, 96 days before disclosure
CVE published
on cve.org
, t = 0
First Exploit-DB entry (opens in a new tab)
Cosy+ firmware 21.2s7 - Command Injection
, 251 days after disclosure
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
- Immediately upgrade all Cosy+ devices to firmware versions 21.2s10 or 22.1s3 or later to apply the official patch addressing the vulnerability.
- Restrict administrative and privileged access to Cosy+ devices by implementing strong network segmentation and access control lists (ACLs) to limit exposure to trusted IP addresses and networks only.
- Employ multi-factor authentication (MFA) for all administrative access to reduce the risk of credential compromise leading to exploitation.
- Monitor device logs and network traffic for unusual commands or activities indicative of code injection attempts or unauthorized access.
- Conduct regular vulnerability assessments and penetration testing focused on operational technology (OT) environments to identify and remediate similar weaknesses.
- Establish an incident response plan specific to industrial control systems that includes procedures for isolating affected devices and restoring secure operations.
- Educate staff responsible for device management about the importance of timely patching and secure configuration practices.
- If immediate patching is not feasible, consider temporary compensating controls such as disabling remote management interfaces or placing devices behind VPNs with strict access policies.
Description
Cosy+ devices running a firmware 21.x below 21.2s10 or a firmware 22.x below 22.1s3 are vulnerable to code injection due to improper parameter blacklisting. This is fixed in version 21.2s10 and 22.1s3.
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/21 (opens in a new tab)