CVE-2024-33892· NVD / CVE Program· CNA mitre

Insecure Permissions vulnerability in Cosy+ devices running a firmware 21.x below 21.2s10 or a firmware 22.x below 22.1s3 are susceptible to

Noroxi assessment

Priority: Monitor (action score 30/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.45% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: n/a n/a 21.2s10.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to n/a n/a 21.2s10 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Insecure Permissions vulnerability in Cosy+ devices running a firmware 21.x below 21.2s10 or a firmware 22.x below 22.1s3 are susceptible to leaking information through cookies. This is fixed in version 21.2s10 and 22.1s3

HighCVSS 7.5 · v3.1—No exploit Fix available

Pre-auth

Published: Aug 2, 2024
Updated: Jun 17, 2026
EPSS: 0.4% · 38th percentile
CWE: CWE-312

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.4%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
hms-networks	ewon cosy\+ firmware	cpe:2.3:o:hms-networks:ewon_cosy\+_firmware
hms-networks	ewon cosy\+ 4g apac	cpe:2.3:h:hms-networks:ewon_cosy\+_4g_apac
hms-networks	ewon cosy\+ 4g eu	cpe:2.3:h:hms-networks:ewon_cosy\+_4g_eu
hms-networks	ewon cosy\+ 4g jp	cpe:2.3:h:hms-networks:ewon_cosy\+_4g_jp
hms-networks	ewon cosy\+ 4g na	cpe:2.3:h:hms-networks:ewon_cosy\+_4g_na
hms-networks	ewon cosy\+ ethernet	cpe:2.3:h:hms-networks:ewon_cosy\+_ethernet
hms-networks	ewon cosy\+ wifi	cpe:2.3:h:hms-networks:ewon_cosy\+_wifi

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

hms-networks ewon cosy+ firmware21.0s0 and later · before 21.2s10
hms-networks ewon cosy+ firmware22.0s0 and later · before 22.1s3

Same product

hms-networks: all records

Other highest-scoring records for the same primary product.

CVE-2024-33897A compromised HMS Networks Cosy+ device could be used to request a Certificate Signing Request from Talk2m for another device, resulting in
36Monitor
CVE-2024-33894Insecure Permission vulnerability in Cosy+ devices running a firmware 21.x below 21.2s10 or a firmware 22.x below 22.1s3 are executing sever
35Monitor
CVE-2024-33896Cosy+ 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 paramet
29Monitor

Published before and after this one in the same product

Later →CVE-2024-33893Aug 2, 2024 · Cosy+ devices running a firmware 21.x below 21.2s10 or a firmware 22.x below 22.1s3 are vulnerable to XSS when displaying the logs due to im
24Monitor
Later →CVE-2024-33895Aug 2, 2024 · 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
26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
n/a n/a	21.2s10 · description	Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).