Bug 2229284 - visudo does not checks configuration for case sensitivity
Summary: visudo does not checks configuration for case sensitivity
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: sudo
Version: 8.8
Hardware: All
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Radovan Sroka
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-04 18:44 UTC by jcastran
Modified: 2023-08-16 14:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-164635 0 None None None 2023-08-04 18:45:55 UTC
Red Hat Issue Tracker SECENGSP-5344 0 None None None 2023-08-04 18:46:01 UTC

Description jcastran 2023-08-04 18:44:15 UTC
Description of problem:
When you use a valid configuration option, but use lower case. visudo accepts this but sudo does not work.



Version-Release number of selected component (if applicable):
sudo-1.8.29-10.el8.x86_64



Steps to Reproduce:
1. visudo 
2. user All=(ALL) ALL
3. visudo saves but this is incorrect syntax.


Actual results:
[user@r8 ~]$ sudo echo hi
user is not allowed to run sudo on r8.  This incident will be reported.


Expected results:
This should prevent invalid lower case characters.

# visudo
>>> /etc/sudoers: syntax error near line 101 <<<
What now?

Additional info:

Comment 1 Radovan Sroka 2023-08-16 14:33:26 UTC
This bug is going to be migrated.

Contact point for migration questions or issues: rsroka
Guidance for Bugzilla users to test their Jira account or create one if needed:

https://redhat.service-now.com/help?id=kb_article_view&sysparm_article=KB0016394
https://redhat.service-now.com/help?id=kb_article_view&sysparm_article=KB0016694
https://redhat.service-now.com/help?id=kb_article_view&sysparm_article=KB0016774


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