Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2023-0341: CWE-121 in EditorConfig EditorConfig C Core

0
High
VulnerabilityCVE-2023-0341cvecve-2023-0341cwe-121
Published: Tue Jan 31 2023 (01/31/2023, 23:22:53 UTC)
Source: CVE Database V5
Vendor/Project: EditorConfig
Product: EditorConfig C Core

Description

A stack buffer overflow exists in the ec_glob function of editorconfig-core-c before v0.12.6 which allowed an attacker to arbitrarily write to the stack and possibly allows remote code execution. editorconfig-core-c v0.12.6 resolved this vulnerability by bound checking all write operations over the p_pcre buffer.

AI-Powered Analysis

AILast updated: 11/04/2025, 00:05:13 UTC

Technical Analysis

CVE-2023-0341 is a stack-based buffer overflow vulnerability identified in the ec_glob function of the EditorConfig C Core library, specifically in versions before 0.12.6. EditorConfig is a widely used open-source tool that helps maintain consistent coding styles across different editors and IDEs by defining configuration files. The vulnerability arises from insufficient bounds checking on the p_pcre buffer during pattern matching operations within the ec_glob function. An attacker who can supply crafted input to this function can cause the program to write beyond the allocated stack buffer, leading to arbitrary memory corruption. This condition can be exploited to execute arbitrary code remotely, compromising the confidentiality, integrity, and availability of the affected system. The vulnerability requires local access with low attack complexity and no privileges, but does require user interaction, such as opening or processing a malicious EditorConfig file. The fix implemented in version 0.12.6 involves adding strict bounds checking on all write operations to the p_pcre buffer, effectively preventing overflow. No known exploits are currently reported in the wild, but the high CVSS score of 7.8 reflects the serious risk posed by this vulnerability. EditorConfig C Core is often integrated into development tools and CI/CD pipelines, making it a critical component in software development environments.

Potential Impact

For European organizations, the impact of CVE-2023-0341 can be significant, especially those heavily reliant on open-source development tools and automated build systems that incorporate EditorConfig C Core. Successful exploitation could allow attackers to execute arbitrary code, potentially leading to unauthorized access, data breaches, or disruption of software development workflows. This could compromise sensitive intellectual property, disrupt critical software delivery pipelines, and affect the integrity of deployed applications. Organizations in sectors such as finance, manufacturing, and technology, which have strong software development activities, may face operational and reputational damage. Additionally, the vulnerability could be leveraged as a foothold for further lateral movement within corporate networks. The requirement for user interaction limits remote exploitation but does not eliminate risk, particularly in environments where developers or automated systems process untrusted EditorConfig files.

Mitigation Recommendations

To mitigate this vulnerability, European organizations should immediately upgrade EditorConfig C Core to version 0.12.6 or later, where the buffer overflow issue has been fixed. Conduct a thorough inventory of all development and CI/CD environments to identify instances of EditorConfig C Core usage, including indirect dependencies in build tools and IDE plugins. Implement strict input validation and sandboxing for any processes that parse EditorConfig files, especially those sourced from untrusted or external contributors. Educate developers and DevOps teams about the risks of processing untrusted configuration files and enforce policies to verify the integrity of such files before use. Regularly monitor security advisories for updates or emerging exploits related to EditorConfig and related tooling. Employ runtime protections such as stack canaries and address space layout randomization (ASLR) to reduce exploitation likelihood. Finally, integrate vulnerability scanning tools into the software supply chain to detect usage of vulnerable EditorConfig versions proactively.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
canonical
Date Reserved
2023-01-17T16:04:01.890Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69092626fe7723195e0b5ada

Added to database: 11/3/2025, 10:01:10 PM

Last enriched: 11/4/2025, 12:05:13 AM

Last updated: 11/6/2025, 2:31:42 PM

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats