Bug 1261998

Summary: visudo accept non valid content
Product: Red Hat Enterprise Linux 7 Reporter: Zbynek Moravec <zmoravec>
Component: sudoAssignee: Daniel Kopeček <dkopecek>
Status: CLOSED ERRATA QA Contact: Stefan Kremen <skremen>
Severity: high Docs Contact:
Priority: medium    
Version: 7.1CC: ebenes, pkis, pvrabec, rsroka, skremen
Target Milestone: rcKeywords: Patch
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: sudo-1.8.6p7-18.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-03 20:31:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
patch that resolves acceptation of incorrect sudoers file in visudo none

Description Zbynek Moravec 2015-09-10 14:53:31 UTC 
Description of problem:

Version-Release number of selected component (if applicable):
sudo-1.8.6p7-13.el7.x86_64
How reproducible:


Steps to Reproduce:
1. $ sudo visudo
2. do some syntax error in the file
3. :wq 
4. you will get "visudo: >>> /etc/sudoers: syntax error near line 119 <<<"
6. type "e" to edit again
5. :wq
6. $ sudo
7. you will get "sudo: >>> /etc/sudoers: syntax error near line 119 <<<"

Actual results:
You will get sudoers with syntax error

Expected results:
File with syntax error should not be saved.
Comment 2 Daniel Kopeček 2015-09-10 15:04:55 UTC 
Reproduced. It's too late for 7.3, so I'll fix that in rhel-7.3.
Comment 3 Radovan Sroka 2015-09-15 11:42:42 UTC 
Created attachment 1073595 [details]
patch that resolves acceptation of incorrect sudoers file in visudo
Comment 8 errata-xmlrpc 2016-11-03 20:31:46 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2016-2593.html