Vulnerability in Landesk Management Suite (CVE-2014-5362)
Summary
Vulnerability in Landesk Management Suite (CVE-2014-5362). Successful exploitation can lead to full system takeover.
Original description
The description as published by the source.
The admin interface in Landesk Management Suite 9.6 and earlier allows remote attackers to conduct remote file inclusion attacks involving ASPX pages from third-party sites via the d parameter to (1) ldms/sm_actionfrm.asp or (2) remote/frm_coremainfrm.aspx; or the (3) top parameter to remote/frm_splitfrm.aspx.
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-2014-5362 has been found in Landesk Management Suite.
Successful exploitation can lead to full system takeover. CVSS score: 7.2/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Landesk Management Suite CVE-2014-5362" on the vendor's site.
CVE-2014-5362 (Landesk Management Suite) — CWE-20 / CVSS v3 7.2
Attack vector: remote (network-reachable) / 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 Landesk Management Suite.
Check the vendor advisory for the affected versions of Landesk Management Suite.
Severity: High (CVSS 7.2/10). Successful exploitation can lead to full system takeover.
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・依存マニフェストで Landesk Management Suite を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory securityfocus.com
- advisory securitytracker.com
- exploit packetstormsecurity.com
- web securityfocus.com