| Summary: | CVE-2011-1676 util-linux: mount does not remove /etc/mtab.tmp after failed mount entry addition | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | Vincent Danen <vdanen> |
| Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | unspecified | CC: | kzak |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-04-27 18:13:01 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Vincent Danen
2011-04-12 22:11:03 UTC
Created util-linux-ng tracking bugs for this issue Affects: fedora-all [bug 695940] I'd like to see reproducer for this bug. mount(8) blocks all signals when writing to mtab, the lockfile should be always removed. I'm able to reproduce this problem on umount(8) only: # ulimit -f 1 # umount /mnt/test # ls -la /etc/mtab* -rw-r--r-- 1 root root 2387 Apr 13 10:06 /etc/mtab -rw------- 1 root root 0 Apr 13 10:07 /etc/mtab~ -rw------- 1 root root 1024 Apr 13 10:07 /etc/mtab.tmp (mtab~ is lockfile, mtab.tmp is temporary file). Karel, do you actually see any issue with leaving mtab.tmp file around? Unlike lock file (mtab~) existence, existence of this temporary file does not block further use of mount / umount and the file is overwritten as needed. I currently fail to see a way to trigger mtab corruption as mentioned in the CVE description. Is there anything I'm missing, or is this non-issue that should be disputed? No, the file is unimportant and always overwritten during mtab update. Thank you, closing as not-a-bug. Reporter also confirms there's no issue with mtab.tmp handling: http://thread.gmane.org/gmane.comp.security.oss.general/4374/focus=4983 Statement: Red Hat Product Security determined that this flaw was not a security vulnerability. See the Bugzilla link for more details. |