CVE Intelligence
Skip to main content
HIGH

CVE-2021-41298

CVE-2021-41298 — ECOA BAS controller - Improper Access Control

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.

Published Updated Sources: cvelistV5, twcert

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

1%

chance of exploitation in 30 days

Affects

ecoa

7 products listed

CVSS base

8.8

HIGH

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

Products (7)

ecs router controller ecs flashriskbuster terminator e6l45riskbuster system rb 3 0 0riskbuster system trane 1 0graphic control softwaresmarthome ii e9246riskterminator

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
8.8CVSS 3.1HIGHcvelistV5

Weakness & attack patterns

  • CWE-284

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1027.009Obfuscated Files or Information: Embedded Payloads
  • T1546.004Event Triggered Execution: .bash_profile and .bashrc
  • T1546.016Event Triggered Execution: Installer Packages

References

1 on the record

Elsewhere on this site

  • ecoaevery CVE for this vendor
  • CWE-284other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.