A critical stack-based buffer overflow vulnerability in GIMP 3.0.6 could allow a remote attacker to execute arbitrary code on a victim machine through a specially crafted LBM file.

The vulnerability exists due to improper validation of user-supplied data length when parsing LBM files, leading to a stack-based buffer overflow. An unauthenticated attacker can exploit this flaw by enticing a user to open a malicious LBM file, resulting in code execution within the context of the application.

Successful exploitation of this vulnerability allows an attacker to execute arbitrary code with the privileges of the user running GIMP. Given the CVSS score of 7.8, this represents a high-severity risk that could lead to full system compromise, unauthorized data access, or the deployment of persistent malware within the corporate environment.

Immediate Action: Update GIMP to the latest version that incorporates the fix provided in the GitLab commit 481cdbbb97746be1145ec3a633c567a68633c521.

Proactive Monitoring: Monitor system logs for unusual application crashes or unexpected child processes spawned by the GIMP process, which may indicate attempted exploitation.

Compensating Controls: Implement file-type restrictions or sandbox environments for users who must open untrusted image files, effectively containing the potential impact of a successful overflow exploit.

Public Exploit Available: No (exploit_available: unknown)

Organizations should prioritize updating GIMP installations to the patched version as soon as it becomes available. Users should be cautioned against opening LBM files from untrusted or unverified sources until the patch is successfully deployed across the environment.