CVE-2022-36784
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 · uneditedElsight – Elsight Halo Remote Code Execution (RCE) Elsight Halo web panel allows us to perform connection validation. through the POST request : /api/v1/nics/wifi/wlan0/ping we can abuse DESTINATION parameter and leverage it to remote code execution.
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 Elsight Halo web panel contains a command injection vulnerability in the /api/v1/nics/wifi/wlan0/ping endpoint. The DESTINATION parameter passed via POST request is not properly sanitized before being used in a ping command, allowing an attacker to inject arbitrary OS commands and achieve remote code execution with the privileges of the web service.
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 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 if the system is Elsight HaloAccess the web panel login page and look for 'Elsight Halo' or 'Halo' branding in the interface, or check the HTTP response headers for 'Halo' references. Alternatively, check your network documentation or device label for the Elsight Halo product name.Affected if The device is identified as an Elsight Halo product.
-
Confirm the web panel service is runningAttempt to access the web panel via HTTP or HTTPS on the device IP address (typically ports 80 or 443). Verify the service responds with a login page or API response.Affected if The Elsight Halo web panel is accessible over the network.
-
Verify the vulnerable ping endpoint existsSend a POST request to /api/v1/nics/wifi/wlan0/ping with a DESTINATION parameter (even a benign one like 127.0.0.1). A response (even an error) indicates the endpoint is present and functional.Affected if The /api/v1/nics/wifi/wlan0/ping endpoint responds to requests.
-
Determine if the web panel is exposed to untrusted networksCheck firewall rules, ACLs, or network segmentation configurations to determine if the Elsight Halo web panel (ports 80/443) is accessible from networks outside your trusted internal network.Affected if The web panel is accessible from untrusted or external network segments.
You are affected if your Elsight Halo device has the web panel accessible and the /api/v1/nics/wifi/wlan0/ping endpoint is functional, regardless of firmware version.
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 dataRestrict network access to the Elsight Halo web panel to trusted IPs only until an official patch is available. Apply vendor-supplied patches immediately upon release and validate input sanitization in the ping functionality.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36784 — 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-36784 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