Code execution via unbounded ReadIJCoord stack copy
Published Feb 16, 2022 · Updated Apr 15, 2025
Stack-based buffer overflow in KiCad Gerber Viewer 6.0.1 and earlier allows attackers to execute code via a crafted Gerber or Excellon file. ReadIJCoord copies an unbounded run of numeric characters into a 256-byte stack buffer, allowing the write pointer to pass the buffer boundary. Execution requires a user to open the malicious file in gerbview, and reliable code execution depends on the exact build and its mitigations.
Summary
What happened
Stack-based buffer overflow in KiCad Gerber Viewer 6.0.1 and earlier allows attackers to execute code via a crafted Gerber or Excellon file. ReadIJCoord copies an unbounded run of numeric characters into a 256-byte stack buffer, allowing the write pointer to pass the buffer boundary. Execution requires a user to open the malicious file in gerbview, and reliable code execution depends on the exact build and its mitigations.
The record
- CVE
- CVE-2022-23804
- Published
- Feb 16, 2022
- Updated
- Apr 15, 2025
- Vendor
- KiCad Development Team
- Product
- KiCad
- Classifications
- CWE-121, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 16, 2022CVE publishedPublication date reported by the CVE source.
- Apr 15, 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=KiCad EDA 6.0.1, KiCad EDA master commit de006fc010
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
- ReadIJCoord.bof.gbrproof of concept · demonstrated
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