Code execution via unchecked DSB data copy
Published Sep 2, 2025 · Updated Sep 2, 2025
Heap-based buffer overflow in all versions of Digilent DASYLab allows attackers to execute code through a crafted DSB file. The DSB parser copies user-supplied data into a heap buffer without validating its length, allowing the copy to exceed the destination boundary. Execution occurs in the DASYLab process context and requires a user to open the malicious file; the issue is not remotely exploitable without that interaction.
Summary
What happened
Heap-based buffer overflow in all versions of Digilent DASYLab allows attackers to execute code through a crafted DSB file. The DSB parser copies user-supplied data into a heap buffer without validating its length, allowing the copy to exceed the destination boundary. Execution occurs in the DASYLab process context and requires a user to open the malicious file; the issue is not remotely exploitable without that interaction.
The record
- CVE
- CVE-2025-57775
- Published
- Sep 2, 2025
- Updated
- Sep 2, 2025
- Vendor
- Digilent
- Product
- DASYLab
- Classifications
- CWE-787, CWE-1285, CAPEC-100, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 2, 2025CVE publishedPublication date reported by the CVE source.
- Sep 2, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=*
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo