Vulnerability in Locus Energy LGate (CVE-2016-5782)
Summary
Vulnerability in Locus Energy LGate (CVE-2016-5782). Confidential information can be exposed externally.
Original description
The description as published by the source.
An issue was discovered in Locus Energy LGate prior to 1.05H, LGate 50, LGate 100, LGate 101, LGate 120, and LGate 320. Locus Energy meters use a PHP script to manage the energy meter parameters for voltage monitoring and network configuration. The PHP code does not properly validate information that is sent in the POST request.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2016-5782 has been found in Locus Energy LGate.
Confidential information can be exposed externally. CVSS score: 8.6/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Locus Energy LGate CVE-2016-5782" on the vendor's site.
CVE-2016-5782 (Locus Energy LGate) — CWE-20 / CVSS v3 8.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in Locus Energy LGate.
Check the vendor advisory for the affected versions of Locus Energy LGate.
Severity: High (CVSS 8.6/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Locus Energy LGate を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory securityfocus.com
- advisory securityfocus.com
- advisory ics-cert.us-cert.gov