Bug 1000722
Summary: | ngircd: failure to drop supplementary groups | ||
---|---|---|---|
Product: | [Other] Security Response | Reporter: | Michael S. <misc> |
Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | andreas, security-response-team, vkrizan |
Target Milestone: | --- | Keywords: | Security |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-12-18 17:16:11 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: | |||
Bug Depends On: | 1044619, 1044620 | ||
Bug Blocks: | 1001205 |
Description
Michael S.
2013-08-24 16:51:30 UTC
Hi, Michael. Please do let upstream know about this issue. If they're unaware of it, I can certainly assign a CVE on their behalf. I do see they just released 20.3 which fixed a DoS condition, so they should be quite responsive to this flaw as well. Will do. Not sure if that deserve a CVE since there is no direct privileges escalation, and I found quite a lot of similar problem in Fedora ( using rpmlint and checking manually ). Last time I found one ( for haproxy ), we concluded this was just a failure to harden the system and didn't gave a CVE. Hi, Michael. Did upstream ever respond to this? I'm also fine with treating it as hardening rather than a security flaw. upstream applied and released without CVE ( it was on 27/08 ). So i think this can be closed. Right, this was fixed in ngIRCd 21-rc1 as per http://ngircd.barton.de/doc/ChangeLog : - Correctly discard supplementary groups on server startup. Both Fedora 19 and 20 have this new version. Upstream commits that may be suitable for EPEL: http://arthur.barton.de/cgi-bin/gitweb.cgi?p=ngircd.git;a=commitdiff;h=e009ccbe66f67a4c5344d6a1f415c50b699765ad http://arthur.barton.de/cgi-bin/gitweb.cgi?p=ngircd.git;a=commitdiff;h=41f75b69740bd205864bd34afbb65ab0a3776136 (the first is the actual fix, the second is also required) Even though we are treating this as hardening, I'm going to file a tracking bug for EPEL as I think it would be worthwhile to get in there. Created ngircd tracking bugs for this issue: Affects: fedora-all [bug 1044619] Affects: epel-all [bug 1044620] |