Bug 2191704 (CVE-2023-29491)

Summary: CVE-2023-29491 ncurses: Local users can trigger security-relevant memory corruption via malformed data
Product: [Other] Security Response Reporter: Pedro Sampaio <psampaio>
Component: vulnerabilityAssignee: Nobody <nobody>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: adudiak, bdettelb, caswilli, dffrench, dkuc, fjansen, gzaronik, hbraun, jburrell, jmitchel, jobaror, jtanner, kaycoth, kshier, mlichvar, ngough, nweather, rgodfrey, stcannon, yguenane
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
A vulnerability was found in ncurses and occurs when used by a setuid application. This flaw allows local users to trigger security-relevant memory corruption via malformed data in a terminfo database file found in $HOME/.terminfo or reached via the TERMINFO or TERM environment variable.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2192456, 2192457, 2192458, 2192459    
Bug Blocks: 2191705    

Description Pedro Sampaio 2023-04-28 20:47:45 UTC
ncurses before 6.4 20230408, when used by a setuid application, allows local users to trigger security-relevant memory corruption via malformed data in a terminfo database file that is found in $HOME/.terminfo or reached via the TERMINFO or TERM environment variable.

https://www.openwall.com/lists/oss-security/2023/04/13/4
https://www.openwall.com/lists/oss-security/2023/04/12/5
http://ncurses.scripts.mit.edu/?p=ncurses.git;a=commit;h=eb51b1ea1f75a0ec17c9c5937cb28df1e8eeec56
http://www.openwall.com/lists/oss-security/2023/04/19/10
http://www.openwall.com/lists/oss-security/2023/04/19/11

Comment 9 Miroslav Lichvar 2023-08-15 14:48:06 UTC
*** Bug 2186313 has been marked as a duplicate of this bug. ***