CVE-2021-41290
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 an arbitrary file write and path traversal vulnerability. Using the POST parameters, unauthenticated attackers can remotely set arbitrary values for location and content type and gain the possibility to execute arbitrary code on the affected device.
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 · high confidenceECOA BAS controller contains an arbitrary file write vulnerability combined with path traversal. Unauthenticated attackers can exploit POST parameters to write files to arbitrary locations with attacker-controlled content types, achieving remote code execution on the affected device.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 controllers on your networkScan your network for devices with ECOA model identifiers (Ecs Router Controller, Riskbuster, Riskterminator). Check network device inventories or perform device discovery scans looking for ECOA-specific MAC vendor OUI or service fingerprints.Affected if Any ECOA Ecs Router Controller, Riskbuster, or Riskterminator device is present on your network
-
Check device firmware versionAccess the device management interface or check the firmware version via SNMP/sysinfo queries. Compare the version number against the affected ranges.Affected if All firmware versions are affected; if the device is one of the three named models, it is vulnerable regardless of version
-
Verify web interface accessibilityAttempt to reach the device's HTTP/HTTPS management port from outside the trusted network segment. Confirm whether unauthenticated access to POST endpoints is possible.Affected if The device management interface is reachable from untrusted networks without authentication
-
Inspect network exposure and segmentationReview firewall rules, ACLs, and network zoning to determine whether the BAS controller is isolated from external/untrusted network segments.Affected if The device has direct access from external networks or untrusted zones without firewall protection
-
Check for unauthorized file modificationsReview file system integrity monitoring logs or compare configuration files on the device for unexpected changes, particularly in system directories or web root locations.Affected if Files have been written to unexpected locations or the web root contains suspicious new files
If you have any ECOA Ecs Router Controller, Riskbuster, or Riskterminator device exposed to untrusted networks, your environment is affected by this vulnerability.
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 dataIsolate the affected BAS controller from untrusted networks, block external access, and apply vendor patches if available; if no patch exists, consider device replacement or compensating controls such as network segmentation and monitoring.
- 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-41290 — 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-41290 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