CVE-2021-41297
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedECOA BAS controller is vulnerable to weak access control mechanism allowing authenticated user to remotely escalate privileges by disclosing credentials of administrative accounts in plain-text.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe ECOA BAS controller has weak access control that allows an authenticated (non-admin) user to retrieve administrative account credentials in plain-text, enabling privilege escalation to administrator-level access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify ECOA BAS controller productDetermine the exact model and firmware version of your Building Automation System controller. Check the device label, management interface, or system documentation for product name (Ecoa Ecs Router Controller, Riskbuster, or Riskterminator).Affected if The product is any version of Ecoa Ecs Router Controller Ecs Firmware, Ecoa Riskbuster Firmware, or Ecoa Riskterminator.
-
Review user account configurationAccess the controller user management interface and list all configured user accounts with their assigned roles or privilege levels. Identify whether any accounts have non-administrator roles.Affected if Non-administrator user accounts exist in the system.
-
Verify credential storage formatExamine where administrative credentials are stored (configuration files, user database, or internal storage). Check whether these credentials appear as plain-text or are encrypted/hashed.Affected if Administrative credentials are stored in plain-text rather than being encrypted.
-
Test low-privilege credential accessLog in with a non-administrator user account and attempt to access the administrative user credentials or credential storage location. Observe whether the system returns plain-text administrative passwords.Affected if A non-admin user can retrieve administrative account credentials in plain-text.
You are affected if you run any version of Ecoa Ecs Router Controller, Riskbuster, or Riskterminator firmware and your system allows authenticated non-admin users to access administrative credentials in plain-text.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper role-based access control (RBAC) to restrict low-privilege users from accessing administrative credentials, and ensure all stored credentials are properly encrypted rather than stored in plain-text.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-41297 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-41297 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data