Code execution via unbounded DCodeNumber copy
Published Feb 4, 2022 · Updated Apr 15, 2025
Stack-based buffer overflow in KiCad 6.0.1 and earlier allows attackers to execute code through a crafted Gerber or Excellon file. The Gerber Viewer's DCodeNumber parser copies every number-like character into a 1,024-byte stack buffer without checking its length before adding a terminator. Exploitation requires a user to open the file in GerbView; a crash is straightforward, while code execution depends on the exact build and its mitigations.
Summary
What happened
Stack-based buffer overflow in KiCad 6.0.1 and earlier allows attackers to execute code through a crafted Gerber or Excellon file. The Gerber Viewer's DCodeNumber parser copies every number-like character into a 1,024-byte stack buffer without checking its length before adding a terminator. Exploitation requires a user to open the file in GerbView; a crash is straightforward, while code execution depends on the exact build and its mitigations.
The record
- CVE
- CVE-2022-23947
- Published
- Feb 4, 2022
- Updated
- Apr 15, 2025
- Vendor
- KiCad Development Team
- Product
- KiCad
- Classifications
- CWE-787, CWE-121, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 4, 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
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