CVE-2022-29555
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 · uneditedThe Deviceconnect microservice through 1.3.0 in Northern.tech Mender Enterprise before 3.2.2. allows Cross-Origin Websocket Hijacking.
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 confidenceThe Deviceconnect microservice in Mender Enterprise versions before 3.2.2 is vulnerable to Cross-Origin WebSocket Hijacking (COWSH). This allows an attacker on a malicious website to hijack an authenticated WebSocket connection to the deviceconnect service, potentially executing commands or reading sensitive data transmitted between the client and backend.
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>= 2.6.0, < 3.2.2CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 the installed Mender Enterprise versionCheck the Mender Server or deviceconnect microservice version via the admin UI, API, or deployment configuration files. Common locations include the Helm chart values, docker-compose files, or the service's /api/version endpoint if exposed.Affected if The version is 2.6.0 or higher but lower than 3.2.2
-
Verify the deviceconnect microservice is deployedInspect your Mender deployment to confirm the deviceconnect service is running. Check docker containers, Kubernetes pods, or service manifests for a component named 'deviceconnect' or similar.Affected if The deviceconnect microservice is present and active in the deployment
-
Confirm WebSocket endpoints are exposedIdentify if WebSocket endpoints (ws:// or wss://) for the deviceconnect service are accessible from the network. Review load balancer, API gateway, or reverse proxy configurations for WebSocket upgrade rules.Affected if WebSocket endpoints for deviceconnect are externally accessible without additional origin restrictions
-
Check WebSocket Origin header validationExamine the deviceconnect service configuration or source code (if accessible) for Origin header validation logic on WebSocket upgrade requests. Look for checks that validate the Origin header against an allowlist before accepting the upgrade.Affected if No Origin header validation is implemented or configured for WebSocket upgrade requests
-
Test for COWSH vulnerabilitySend a WebSocket upgrade request to the deviceconnect endpoint with a malicious or unexpected Origin header (e.g., Origin: https://attacker.com) and observe if the server accepts the upgrade without rejecting it.Affected if The server accepts the WebSocket upgrade with an arbitrary or untrusted Origin header
You are affected if running Mender Enterprise version 2.6.0 through 3.2.1 with the deviceconnect microservice exposed and WebSocket connections accepted without strict Origin header 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 · scoped3.2.2
Upgrade the Mender Enterprise deployment to version 3.2.2 or later which contains the patched Deviceconnect microservice (1.3.1+). Implement proper Origin header validation on WebSocket upgrade requests in the interim.
Mender Enterprise 3.2.2 or later
- Upgrade Mender Enterprise to version 3.2.2 or later to remediate the Cross-Origin Websocket Hijacking vulnerability in the Deviceconnect microservice
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29555 — 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-2022-29555 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