Skip to content
Permalink
Browse files Browse the repository at this point in the history
Bug fix for CVE-2014-0039
Bug fix for vulnerability CVE-2014-0039 reported by Murray McAllister of
the Red Hat Security Team in which an attacker-controlled fwsnort.conf
file could be read by fwsnort when not running as root.  This was caused
by fwsnort reading './fwsnort.conf' when not running as root and when a
path to the config file was not explicitly set with -c on the command
line.  This behavior has been changed to require the user to specify a
path to fwsnort.conf with -c when not running as root.
  • Loading branch information
mrash committed Feb 1, 2014
1 parent 8a5e58a commit fa97745
Show file tree
Hide file tree
Showing 4 changed files with 23 additions and 2 deletions.
9 changes: 9 additions & 0 deletions CREDITS
Expand Up @@ -90,3 +90,12 @@ Dwight Davis
handling --strict mode opertions correctly, and more. These issues and
the corresponding patch were originally reported here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693000

Murray McAllister (Red Hat Security Team)
- Reported a bug fix for vulnerability CVE-2014-0039 in which an attacker-
controlled fwsnort.conf file could be read by fwsnort when not running as
root. This was caused by fwsnort reading './fwsnort.conf' when not
running as root and when a path to the config file was not explicitly set
with -c on the command line. This behavior has been changed to require
the user to specify a path to fwsnort.conf with -c when not running as
root.
9 changes: 9 additions & 0 deletions ChangeLog
@@ -1,3 +1,12 @@
fwsnort-1.6.4 (02//2014):
- Bug fix for vulnerability CVE-2014-0039 reported by Murray McAllister of
the Red Hat Security Team in which an attacker-controlled fwsnort.conf
file could be read by fwsnort when not running as root. This was caused
by fwsnort reading './fwsnort.conf' when not running as root and when a
path to the config file was not explicitly set with -c on the command
line. This behavior has been changed to require the user to specify a
path to fwsnort.conf with -c when not running as root.

fwsnort-1.6.3 (12/21/2012):
- Bug fix to ensure that !, <, >, and = chars in content strings are
converted to the appropriate hex equivalents. All content strings with
Expand Down
4 changes: 3 additions & 1 deletion fwsnort
Expand Up @@ -4660,8 +4660,10 @@ sub is_root() {
}

sub set_non_root_values() {

if ($fwsnort_conf eq $CONFIG_DEFAULT) {
$fwsnort_conf = './fwsnort.conf';
die "[*] Must specify a path to readable ",
"fwsnort.conf file when not running as root.";
}

&set_defaults_without_ipt_test();
Expand Down
3 changes: 2 additions & 1 deletion fwsnort.8
Expand Up @@ -82,7 +82,8 @@ By default fwsnort makes use of the configuration file
.B /etc/fwsnort/fwsnort.conf
for almost all configuration parameters. fwsnort can be made to
override this path by specifying a different file on the command
line with the \-\-config option.
line with the \-\-config option. When fwsnort is not executed as root, then
a path to a readable fwsnort.conf file is required.
.TP
.BR \-\^\-update-rules
Download the latest Emerging Threats rules from http://www.emergingthreats.net
Expand Down

0 comments on commit fa97745

Please sign in to comment.