CVE-2021-41294
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 suffers from a path traversal vulnerability, causing arbitrary files deletion. Using the specific GET parameter, unauthenticated attackers can remotely delete arbitrary files on the affected device and cause denial of service scenario.
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 contains a path traversal vulnerability (CWE-22) that allows unauthenticated remote attackers to delete arbitrary files on the affected system via a specifically crafted GET parameter. This vulnerability enables complete file system access for deletion purposes, leading to denial of service through file removal or system corruption.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 controllers on your networkInventory your network for devices with product names: 'Ecoa Ecs Router Controller', 'Ecoa Riskbuster', or 'Ecoa Riskterminator'. Check device documentation, DHCP leases, or network scans for these product identifiers.Affected if Any of these three ECOA BAS controller types exist on your network.
-
Check if web management interface is exposedProbe the suspected ECOA devices on common web ports (80, 443, 8080). Look for login pages or API endpoints that respond to HTTP GET requests without requiring authentication.Affected if The controller's web interface is accessible over the network without authentication required.
-
Verify controller endpoint accessibilitySend a benign HTTP GET request to the controller's base URL and observe the response. Check whether the endpoint returns valid content without any authentication tokens or session cookies.Affected if HTTP requests to the controller return success responses without authentication credentials.
-
Inspect for path traversal handling in requestsIf you have access to controller logs or can safely test, examine how the controller handles GET parameters containing '../' sequences. Check logs for any path traversal patterns in incoming requests.Affected if The controller processes GET parameters containing '../' without rejecting or sanitizing them.
You are affected if you have any Ecoa Ecs Router Controller, Riskbuster, or Riskterminator device with an accessible web interface that processes unauthenticated GET requests containing path traversal sequences.
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 strict input validation on all GET parameters to prevent path traversal sequences (../), enforce authentication on all controller endpoints, and apply vendor patches if available. Network segmentation should restrict access to the BAS controller from untrusted networks.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-41294 — 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-41294 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