ECOA BAS controller - Improper Access Control

published 2021-09-30 5y ago modified 2026-06-17 4mo ago also EUVD-2021-28328

cvss: 8.8; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.9%; EPSS 0.9% chance of exploitation in 30 days, percentile 59%
public exploits: 0; none known

ECOA BAS controller is vulnerable to insecure direct object references that occur when the application provides direct access to objects based on user-supplied input. As a result of this vulnerability, attackers with general user's privilege can remotely bypass authorization and access the hidden resources in the system and execute privileged functionalities.

Is CVE-2021-41298 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.87% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.8	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	6.5	AV:N/AC:L/Au:S/C:P/I:P/A:P

Affected products

ECOA ECS Router Controller ECS (FLASH)
ECOA RiskBuster Terminator E6L45
ECOA RiskBuster System RB 3.0.0
ECOA RiskBuster System TRANE 1.0
ECOA Graphic Control Software
ECOA SmartHome II E9246
ECOA RiskTerminator

Classification

Weakness

CWE-284 Improper Access Control
CWE-639 Authorization Bypass Through User-Controlled Key

References

twcert.org.tw /tw/cp-132-5134-39f74-1.html
third-party-advisory

Sources

CVE List CVE-2021-41298
NVD CVE-2021-41298

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.