CVE-2012-10057
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-08-13

Last updated on: 2025-08-14

Assigner: VulnCheck

Description
Lattice Semiconductor ispVM System v18.0.2 contains a buffer overflow vulnerability in its handling of .xcf project files. When parsing the version attribute of the ispXCF XML tag, the application fails to properly validate input length, allowing a specially crafted file to overwrite memory on the stack. This can result in arbitrary code execution under the context of the user who opens the file. The vulnerability is triggered locally by opening a malicious .xcf file and does not require elevated privileges.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-08-13
Last Modified
2025-08-14
Generated
2026-05-06
AI Q&A
2025-08-13
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
lattice_semiconductor ispvm_system 18.0.2
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-121 A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2012-10057 is a stack-based buffer overflow vulnerability in Lattice Semiconductor ispVM System version 18.0.2. It occurs when the application improperly handles .xcf project files, specifically by failing to validate the length of the "version" attribute within the <ispXCF> XML tag. A specially crafted .xcf file with an excessively long version attribute can overwrite memory on the stack, allowing an attacker to execute arbitrary code under the context of the user who opens the file. Exploitation requires local access and user interaction to open the malicious file, but does not require elevated privileges. [1, 2, 3]


How can this vulnerability impact me? :

This vulnerability can allow an attacker to execute arbitrary code on your system with the same privileges as the user who opens the malicious .xcf file. This could lead to unauthorized actions such as installing malware, stealing data, or disrupting system operations. Since the exploit runs with user-level privileges, the impact depends on the permissions of the affected user. The vulnerability requires the user to open a crafted file locally, so social engineering or tricking the user into opening the file is necessary. [1, 3, 4]


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

This vulnerability is triggered locally by opening a specially crafted .xcf file with an excessively long "version" attribute in the <ispXCF> XML tag. Detection involves identifying such malicious .xcf files before they are opened. You can scan your system or network for .xcf files and inspect the "version" attribute length within the <ispXCF> tag. For example, using PowerShell or grep to extract and check the length of the version attribute in .xcf files could help detect suspicious files. However, no specific detection commands or signatures are provided in the resources. [1, 2, 4]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include not opening .xcf files from untrusted or unknown sources, as the vulnerability is triggered by opening a maliciously crafted file. Since the vulnerability requires user interaction and local execution, educating users to avoid opening suspicious .xcf files is critical. Additionally, applying any available patches or updates from Lattice Semiconductor (if available) is recommended. If no patch exists, consider restricting access to ispVM System 18.0.2 or running it in a controlled environment to limit potential impact. [4, 3]


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