LiveActive security incident?Get immediate response
CVE Record

CVE-2016-5248: The StopProxy command in LSC.Services.SystemService in Lenovo Solution Center before 3.3.003 allows local u...

The StopProxy command in LSC.Services.SystemService in Lenovo Solution Center before 3.3.003 allows local users to terminate arbitrary processes via the PID argument.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Older Lenovo Solution Center installations allowed someone already on the machine to make a Lenovo service terminate chosen processes. Based on the provided sources, this is a local availability/control issue, not evidence of a remote break-in path.

Executive priority

Treat as a targeted endpoint hygiene issue. It is worth remediating on shared or high-risk workstations, but the provided evidence does not support emergency internet-wide response.

Technical view

CVE-2016-5248 affects Lenovo Solution Center before 3.3.003. The StopProxy command in LSC.Services.SystemService accepts a PID argument and allowed local users to terminate arbitrary processes. No CVSS, CWE, or detailed product matrix was provided.

Likely exposure

Likely exposure is Lenovo endpoints running Lenovo Solution Center earlier than 3.3.003. The bundle does not identify exact device models, operating systems, or default install scope.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. Exploitation requires local user access according to the CVE description, so internet-facing exposure is not supported by the provided evidence.

Researcher notes

The record is concise and lacks CVSS/CWE details. The core primitive is arbitrary local process termination through a service command PID parameter. Avoid assuming privilege escalation or active exploitation without additional vendor or researcher evidence.

Mitigation direction

  • Update Lenovo Solution Center to version 3.3.003 or later.
  • If unused, remove Lenovo Solution Center from managed endpoints.
  • Check Lenovo advisory LEN-7814 for vendor-specific remediation details.
  • Prioritize devices where untrusted local users can log in.

Validation and detection

  • Inventory endpoints for Lenovo Solution Center installations.
  • Confirm installed versions are 3.3.003 or later.
  • Review software management records for successful removal or upgrade.
  • Check endpoint logs for unexpected termination of security or management processes.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2016-5248 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.