LiveActive security incident?Get immediate response
CVE Record

CVE-2021-41299: ECOA BAS controller - Use of Hard-coded Credentials

ECOA BAS controller is vulnerable to hard-coded credentials within its Linux distribution image, thus remote attackers can obtain administrator’s privilege without logging in.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2021-41299 is a critical hard-coded credential issue in ECOA BAS controller products. A remote attacker may gain administrator privileges without logging in. For organizations using these building automation products, the business risk is loss of control over operational building systems.

Executive priority

Treat this as urgent for any site using affected ECOA building automation products. The vulnerability can grant administrator control without authentication, but remediation details are not provided in the bundle, so vendor confirmation is necessary.

Technical view

The issue is CWE-798: hard-coded credentials in the Linux distribution image used by listed ECOA BAS controller products. The CVSS 3.1 score is 9.8 with network attack vector, no required privileges, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely in facilities running the listed ECOA ECS, RiskBuster, RiskTerminator, Graphic Control Software, or SmartHome II products. Risk is higher if controller management access is reachable from untrusted networks.

Exploitation context

The provided bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector indicates the vulnerability is remotely reachable and does not require authentication, but no exploit status is confirmed here.

Researcher notes

Affected version data is sparse and appears as “next of 0” in the bundle, so product identification matters more than version matching. Do not assume a password change fixes hard-coded credentials unless vendor guidance confirms it.

Mitigation direction

  • Confirm whether ECOA or TWCERT has released firmware, replacement, or hardening guidance for affected models.
  • Remove affected controllers from direct internet or untrusted network access.
  • Place BAS controllers behind segmented management networks and restrict access with firewall or VPN controls.
  • Monitor administrative access and configuration changes for unexpected activity.
  • Plan replacement if vendor confirms hard-coded credentials cannot be removed.

Validation and detection

  • Inventory ECOA BAS products and match names against the affected product list.
  • Verify whether any affected controller is reachable from untrusted networks.
  • Review firmware images, vendor documentation, and device accounts for hard-coded credential exposure.
  • Check logs for unexpected administrator sessions or configuration changes.
  • Record firmware versions and vendor support status for each affected asset.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-798: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-41299 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2021-41299Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ECOAECS Router Controller ECS (FLASH)next of 0Listed
ECOARiskBuster Terminator E6L45next of 0Listed
ECOARiskBuster System RB 3.0.0next of 0Listed
ECOARiskBuster System TRANE 1.0next of 0Listed
ECOAGraphic Control Softwarenext of 0Listed
ECOASmartHome II E9246next of 0Listed
ECOARiskTerminatornext of 0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-798 · source CWE mapping

Use of Hard-coded Credentials

Use of Hard-coded Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.