Bug 232031 - [SECURITY]SELinux errors, using of system() call in src/ntfs-3g.c
[SECURITY]SELinux errors, using of system() call in src/ntfs-3g.c
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: ntfs-3g (Show other bugs)
6
All Linux
high Severity high
: ---
: ---
Assigned To: Tom "spot" Callaway
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-03-13 13:35 EDT by Jochen Schmitt
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version: 1.516-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-06-26 12:14:01 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
avc messages from /var/log/messages (3.64 KB, text/plain)
2007-03-13 13:35 EDT, Jochen Schmitt
no flags Details
Patch for solve security weakness (1.16 KB, patch)
2007-03-13 14:29 EDT, Jochen Schmitt
no flags Details | Diff

  None (edit)
Description Jochen Schmitt 2007-03-13 13:35:33 EDT
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 13:35:33 EDT
Created attachment 149954 [details]
avc messages from /var/log/messages
Comment 2 Jochen Schmitt 2007-03-13 14:29:37 EDT
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 12:14:01 EDT
This is fixed in 1.516-1 or later ntfs-3g packages.

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