CVE-2021-44458
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 · uneditedLinux users running Lens 5.2.6 and earlier could be compromised by visiting a malicious website. The malicious website could make websocket connections from the victim's browser to Lens and so operate the local terminal feature. This would allow the attacker to execute arbitrary commands as the Lens user.
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 confidenceA cross-origin websocket vulnerability in Lens 5.2.6 and earlier allows malicious websites to connect to the local Lens terminal service via the browser. Since Lens binds to localhost without proper origin validation, attackers can execute arbitrary commands as the Lens user by sending terminal commands through the websocket connection.
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 data<= 5.2.6CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 installed Lens versionCheck the Lens application version through its built-in About or Help menu, or via your system package manager if installed system-wideAffected if The installed version is 5.2.6 or earlier
-
Locate the Lens terminal service portRun netstat or ss commands to identify ports bound to localhost that may be used by Lens terminal service (typically looks for local ports in the 50000-60000 range or check Lens documentation for default terminal port)Affected if Lens terminal service is listening on localhost without origin restrictions
-
Verify websocket endpoint accessibilityUse curl or a simple websocket client to attempt a connection to the local Lens terminal service endpoint from a non-Lens originAffected if Connections from arbitrary origins are accepted without validation
-
Check for origin validation in configurationExamine Lens configuration files for any origin or CORS settings related to the terminal websocket endpointAffected if No origin validation or CORS policy is configured for the terminal service
-
Confirm browser-based terminal accessTest whether a web page hosted on a different origin can successfully send commands through the Lens websocket to execute terminal operationsAffected if Arbitrary websites can execute commands through the websocket connection
A user is affected if they are running Mirantis Lens version 5.2.6 or earlier and the terminal websocket service accepts connections without proper origin validation.
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.
dbcve · scopedUpgrade Lens to version 5.2.7 or later. If immediate upgrade is not possible, consider network-level controls to restrict localhost access to the terminal service.
Lens 5.2.7 or later (any stable release newer than 5.2.6)
- Upgrade Lens to version 5.2.7 or later to receive the security patch
- After upgrading, verify the websocket authentication is properly enforced
- Ensure all local terminal sessions require explicit authentication before allowing command execution
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-44458 — 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-44458 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