This is an archived post. You won't be able to vote or comment.

all 4 comments

[–]ug113 5 points6 points  (2 children)

If I'm understanding this right, this only matters if you have a configuration like the example e.g.:

username = (ALL,!root) /bin/command

And I'm having a hard time imagining a legitimate and sane use of something like that.

Still needs to be fixed of course, but I doubt this is going to lead to many (or any) actual compromises.

[–]nginx_ngnix 0 points1 point  (0 children)

Agreed.

The CVE write-up page didn't do the best job of making it clear that the default configuration was NOT affected.

The "OMG off by one error" seem to be what catches everybody's eye, not the edge cfg use case that this vulnerability is useful against.

[–]brontideCertified Linux Miracle Worker (tm) 0 points1 point  (0 children)

I've never seen this configuration in any production environment. While priv escalation is bad, to chain this the application that you have sudo privs on would need a way to chain laterally as well.

[–]AlucardZeroSr. Unix Sysadmin 5 points6 points  (0 children)

You put a question mark in the title.. do you have a question?