Description

There is an out-of-bounds read vulnerability in DASYLab due to improper validation of user-supplied data.   This results in a read outside the bounds of an allocated data structure.  Successful exploitation requires an attacker to get a user to open a specially crafted .DSB file.  This issue affects all versions before 2026.0.0.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "7.8",
  "pubDate": "2026-09-03T22:18:10.337Z",
  "pubdate": "2026-09-03T22:18:10.337Z",
  "executiveSummary": "DASYLab contains an out-of-bounds read vulnerability stemming from improper validation of user-supplied data during the parsing of .DSB project files.\nThis vulnerability allows an attacker to trigger an unauthorized memory access, potentially resulting in application crashes, denial-of-service, or the leakage of sensitive information residing in memory.\nThe flaw affects all versions of DASYLab prior to 2026.0.0.\nExploitation is contingent upon social engineering, as it requires an attacker to successfully induce a legitimate user into opening a maliciously crafted .DSB file.\nThe risk implication is significant for users relying on the software, as the vulnerability resides in the core file processing logic, making it a viable target for attackers aiming to exfiltrate data or disrupt operational workflows via file-borne attacks.",
  "technicalDetails": "The vulnerability is classified as an out-of-bounds read, rooted in the application's failure to perform adequate boundary checks on data extracted from .DSB file structures.\nWhen DASYLab parses a .DSB file, it processes various data elements stored within the file format. If these elements contain manipulated length or offset parameters that exceed the memory allocated for the corresponding buffer, the application attempts to read data from adjacent memory locations.\nThe attack flow begins when an attacker distributes a specially crafted .DSB file to a target user. Upon opening this file, DASYLab's parser fails to validate the integrity of the data structures, leading to the out-of-bounds access.\nFrom a memory safety perspective, the application likely utilizes a static or heap-based buffer for processing file contents. If the malicious input provides an index or pointer outside the permitted range, the read operation proceeds, potentially reading information from the application's process heap or stack.\nThe impact of such an out-of-bounds read is two-fold: first, it can cause an access violation leading to an application crash, facilitating a denial-of-service condition. Second, by controlling the input, an attacker may be able to influence the application's execution path if the leaked memory is subsequently processed or leaked via error messages, diagnostics, or other return vectors.\nThis vulnerability is present in all versions prior to 2026.0.0. Exploitation does not require authentication or specific privilege escalation beyond the standard user level, as the process occurs within the context of the user executing the application. The vulnerability is local in nature, requiring the target file to be opened directly within the affected DASYLab software."
}