Project

General

Profile

Actions

Bug #1021

closed

1.4.6: conf_filename not checked before use

Added by Mark Solaris over 10 years ago. Updated about 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Affected Versions:
Effort:
Difficulty:
Label:

Description

If no -c argument is provided, no default conf file is used, or an error given.

(dbx) run u
Running: suricata -u
(process id 13852)
1/11/2013 -
07:28:58 - <Info> - This is Suricata version 1.4.6 RELEASE
1/11/2013 -- 07:28:58 - <Info> - CPUs/cores online: 64
t@1 (l@1) signal SEGV (no mapping at the fault address) in strlen at 0xffffffff7d93c750
0xffffffff7d93c750: strlen+0x0050: ld [%o2], %o1
Current function is main
1399 SCLogError(SC_ERR_LOGDIR_CONFIG, "The logging directory \"%s\" "
(dbx) list
1399 SCLogError(SC_ERR_LOGDIR_CONFIG, "The logging directory \"%s\" "
1400 "supplied by %s (default-log-dir) doesn't exist. "
1401 "Shutting down the engine", log_dir, conf_filename);
1402 exit(EXIT_FAILURE);
1403 }
1404 }
1405
1406 /* Pull the max pending packets from the config, if not found fall
1407 * back on a sane default. */
1408 if (ConfGetInt("max-pending-packets", &max_pending_packets) != 1)
(dbx) print log_dir
log_dir = 0x101e11ae8 "/var/log/suricata"
(dbx) print conf_filename
conf_filename = (nil)
Actions

Also available in: Atom PDF