Bug 2193152 (CVE-2023-0341) - CVE-2023-0341 editorconfig-core-c:arbitrary stack write
Summary: CVE-2023-0341 editorconfig-core-c:arbitrary stack write
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2023-0341
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2193153 2193154
Blocks: 2192389
TreeView+ depends on / blocked
 
Reported: 2023-05-04 13:39 UTC by Anten Skrabec
Modified: 2023-05-04 18:31 UTC (History)
1 user (show)

Fixed In Version: editorconfig 0.12.6
Doc Type: ---
Doc Text:
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.
Clone Of:
Environment:
Last Closed: 2023-05-04 18:31:37 UTC
Embargoed:


Attachments (Terms of Use)

Description Anten Skrabec 2023-05-04 13:39:12 UTC
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.

Comment 1 Anten Skrabec 2023-05-04 13:39:29 UTC
Created editorconfig tracking bugs for this issue:

Affects: epel-all [bug 2193153]
Affects: fedora-all [bug 2193154]

Comment 2 Ben Beasley 2023-05-04 13:50:41 UTC
Kalev, I don’t see any reason not to simply build 0.12.6 for all releases. Do you?

Comment 3 Product Security DevOps Team 2023-05-04 18:31:35 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.


Note You need to log in before you can comment on or make changes to this bug.