CVE-2018-25255
Received Received - Intake
Local Buffer Overflow in 10-Strike LANState Enables Code Execution

Publication date: 2026-04-04

Last updated on: 2026-04-04

Assigner: VulnCheck

Description
10-Strike LANState 8.8 contains a local buffer overflow vulnerability in structured exception handling that allows local attackers to execute arbitrary code by crafting malicious LSM map files. Attackers can create a specially formatted LSM file with a payload in the ObjCaption parameter that overflows the buffer, overwrites the SEH chain, and executes shellcode when the file is opened in the application.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-04
Last Modified
2026-04-04
Generated
2026-05-07
AI Q&A
2026-04-04
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
10-strike lanstate to 8.8 (exc)
10-strike lanstate 8.8
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-787 The product writes data past the end, or before the beginning, of the intended buffer.
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability in 10-Strike LANState 8.8 allows local attackers to execute arbitrary code, which can lead to unauthorized access, modification, or disruption of data handled by the application.

Such unauthorized code execution and potential data compromise could negatively impact compliance with standards and regulations like GDPR and HIPAA, which require protection of confidentiality, integrity, and availability of sensitive data.

However, the provided information does not explicitly describe the direct effects on compliance or specific regulatory impacts.


Can you explain this vulnerability to me?

CVE-2018-25255 is a local buffer overflow vulnerability in 10-Strike LANState version 8.8. It occurs in the structured exception handling (SEH) mechanism when the application processes specially crafted LSM map files.

An attacker can create a malicious LSM file with a payload in the ObjCaption parameter that overflows a buffer, overwrites the SEH chain, and executes arbitrary code (shellcode) when the file is opened in the application.

This vulnerability allows local attackers to run code on the affected system by exploiting the buffer overflow triggered during file processing.


How can this vulnerability impact me? :

This vulnerability can have severe impacts because it allows local attackers to execute arbitrary code on the affected system without requiring privileges or user interaction.

  • Attackers can gain control over the system by running malicious shellcode.
  • Confidentiality, integrity, and availability of the system can be compromised.
  • It can lead to unauthorized access, data theft, or disruption of services.

How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability is a local buffer overflow in the 10-Strike LANState application triggered by opening a specially crafted .lsm file. Detection involves identifying if the vulnerable version 8.8 or earlier of LANState is installed on the system.

Since the exploit requires opening a malicious .lsm file locally, network detection is limited. However, monitoring for suspicious .lsm file openings or unusual process behavior related to LANState could help.

No specific detection commands are provided in the resources. As a general approach, you can check the installed version of LANState with commands like:

  • On Windows, use PowerShell to check installed software: Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object { $_.DisplayName -like '*LANState*' } | Select-Object DisplayName, DisplayVersion
  • Search for .lsm files on the system that might be suspicious: dir C:\ /s /b *.lsm

Additionally, monitoring process creation events for LANState.exe opening files or unusual behavior could indicate exploitation attempts.


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include:

  • Avoid opening any untrusted or suspicious .lsm files in the LANState application.
  • If possible, upgrade LANState to a version later than 8.8 where this vulnerability is fixed (no fixed version explicitly mentioned, so check vendor updates).
  • Restrict local user access to the LANState application to trusted users only.
  • Implement application whitelisting or sandboxing to prevent execution of malicious payloads.

Since the vulnerability requires local file opening, controlling file access and user permissions is critical.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart