Bug 232031

Summary: [SECURITY]SELinux errors, using of system() call in src/ntfs-3g.c
Product: [Fedora] Fedora Reporter: Jochen Schmitt <jochen>
Component: ntfs-3gAssignee: Tom "spot" Callaway <tcallawa>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: high    
Version: 6   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 1.516-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-06-26 16:14: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:
Embargoed:
Attachments:
Description Flags
avc messages from /var/log/messages
none
Patch for solve security weakness none

Description Jochen Schmitt 2007-03-13 17:35:33 UTC 
In my message log I have found avc message, witch was coused by ntfs-3g.

After a look on the messages, I was wondering, that mount.ntfs want to start the
bash. In the code I found a test on the /sbin/modprobe exectuable. If this
exceubable exist, a system("modeprobe fuse") will done.

The usage of the system() call is a bad idea, becouse it is make possible to
manipulate the localion from where the modprobe will be execute. The usage of an
exec()-like call may be better.

Best Regards:

Jochen Schmitt
Comment 1 Jochen Schmitt 2007-03-13 17:35:33 UTC 
Created attachment 149954 [details]
avc messages from /var/log/messages
Comment 2 Jochen Schmitt 2007-03-13 18:29:37 UTC 
Created attachment 149967 [details]
Patch for solve security weakness

I have added an untested patch which replace the system()-call ba the
fork()/execl()-call.
Comment 3 Tom "spot" Callaway 2007-06-26 16:14:01 UTC 
This is fixed in 1.516-1 or later ntfs-3g packages.