A NOTE has been added to this issue. 
====================================================================== 
https://www.austingroupbugs.net/view.php?id=1435 
====================================================================== 
Reported By:                zackw
Assigned To:                
====================================================================== 
Project:                    1003.1(2016/18)/Issue7+TC2
Issue ID:                   1435
Category:                   System Interfaces
Type:                       Error
Severity:                   Objection
Priority:                   normal
Status:                     New
Name:                       Zack Weinberg 
Organization:               GNU 
User Reference:              
Section:                    exec 
Page Number:                (unknown) 
Line Number:                (unknown) 
Interp Status:              --- 
Final Accepted Text:         
====================================================================== 
Date Submitted:             2020-12-15 14:50 UTC
Last Modified:              2020-12-16 02:08 UTC
====================================================================== 
Summary:                    execlp and execvp should not execute a command
interpreter when other members of the exec family would fail with ENOEXEC
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0001226 shell can not test if a file is text
====================================================================== 

---------------------------------------------------------------------- 
 (0005180) dannyniu (reporter) - 2020-12-16 02:08
 https://www.austingroupbugs.net/view.php?id=1435#c5180 
---------------------------------------------------------------------- 
As a read-only member on the mailing list who currently supervises the
security logic of the web app deployed on our Linux server, I totally agree
this is a serious potential security exploit. 

I suggest a moderate modification. That is: 

Change: 

> execlp() and execvp() functions shall execute a command interpreter ...

To

> execlp() and execvp() functions may execute the "sh" command interpreter
... 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2020-12-15 14:50 zackw          New Issue                                    
2020-12-15 14:50 zackw          Name                      => Zack Weinberg   
2020-12-15 14:50 zackw          Organization              => GNU             
2020-12-15 14:50 zackw          Section                   => exec            
2020-12-15 14:50 zackw          Page Number               => (unknown)       
2020-12-15 14:50 zackw          Line Number               => (unknown)       
2020-12-15 15:22 geoffclare     Note Added: 0005173                          
2020-12-15 15:22 geoffclare     Relationship added       related to 0001226  
2020-12-15 15:31 zackw          Note Added: 0005174                          
2020-12-15 15:45 geoffclare     Note Added: 0005175                          
2020-12-15 15:53 zackw          Note Added: 0005176                          
2020-12-15 15:54 zackw          Note Added: 0005177                          
2020-12-15 15:56 zackw          Note Added: 0005178                          
2020-12-15 16:11 shware_systems Note Added: 0005179                          
2020-12-16 02:08 dannyniu       Note Added: 0005180                          
======================================================================


  • [1003.1(2016... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group

Reply via email to