CVE-2023-44443
Memory Safety in Gimp ≤ 2.10.36
Raw vector
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2023-44443 is a high-severity Integer Overflow or Wraparound (CWE-190) vulnerability in Gimp Gimp. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 0.2% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2023-44443 is an integer overflow vulnerability in GIMP's handling of PSP files, tracked as ZDI-CAN-22096 and assigned CWE-190. The flaw stems from insufficient validation of user-supplied data during PSP parsing, which can produce an integer overflow prior to a memory write and allow arbitrary code execution. Affected installations are those of GIMP prior to the version containing the fix.
Remote attackers can exploit the issue by supplying a malicious PSP file. Successful exploitation requires user interaction, such as opening the file locally or visiting a page that delivers it, after which code runs in the context of the GIMP process. The vulnerability carries a CVSS 3.0 base score of 7.8 reflecting local access, low attack complexity, no privileges required, and required user interaction, with high impact on confidentiality, integrity, and availability.
The referenced GIMP 2.10.36 release announcement and the corresponding Zero Day Initiative advisory ZDI-23-1593 indicate that the issue is resolved in GIMP version 2.10.36. The current EPSS score of 0.6376 with a peak of 0.6544 does not reflect a material rise from a low baseline.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-48783
Vulnerability Data
GIMP PSP File Parsing Integer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of GIMP. User interaction is required to exploit this vulnerability in that the target must visit a malicious…
more
page or open a malicious file. The specific flaw exists within the parsing of PSP files. The issue results from the lack of proper validation of user-supplied data, which can result in an integer overflow before writing to memory. An attacker can leverage this vulnerability to execute code in the context of the current process. . Was ZDI-CAN-22096.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.2.6
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (static analysis, fuzzing, unit tests) directly finds integer overflow defects before deployment.
Secure engineering principles require use of safe arithmetic constructs or language features that structurally eliminate integer overflow during calculation.
Input validation enforces bounds on values before arithmetic, stopping the conditions that trigger overflow or wraparound.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require use of safe arithmetic, bounds checks, and testing that prevent integer overflows.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect integer overflows before release.
Secure SDLC mandates input validation and arithmetic checks that prevent integer overflows.
Application security requirements include bounds checking and safe arithmetic to avoid overflow conditions.
Secure architecture principles require defensive coding patterns that mitigate integer wraparound risks.
Secure coding standards explicitly forbid unsafe integer operations and mandate overflow-safe constructs.