mod-security-users Mailing List for ModSecurity (Page 581)
Brought to you by:
victorhora,
zimmerletw
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
(17) |
Aug
(7) |
Sep
(8) |
Oct
(11) |
Nov
(14) |
Dec
(19) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(46) |
Feb
(14) |
Mar
(20) |
Apr
(48) |
May
(15) |
Jun
(20) |
Jul
(36) |
Aug
(24) |
Sep
(31) |
Oct
(28) |
Nov
(23) |
Dec
(12) |
| 2005 |
Jan
(69) |
Feb
(61) |
Mar
(82) |
Apr
(53) |
May
(26) |
Jun
(71) |
Jul
(27) |
Aug
(52) |
Sep
(28) |
Oct
(49) |
Nov
(104) |
Dec
(74) |
| 2006 |
Jan
(61) |
Feb
(148) |
Mar
(82) |
Apr
(139) |
May
(65) |
Jun
(116) |
Jul
(92) |
Aug
(101) |
Sep
(84) |
Oct
(103) |
Nov
(174) |
Dec
(102) |
| 2007 |
Jan
(166) |
Feb
(161) |
Mar
(181) |
Apr
(152) |
May
(192) |
Jun
(250) |
Jul
(127) |
Aug
(165) |
Sep
(97) |
Oct
(135) |
Nov
(206) |
Dec
(56) |
| 2008 |
Jan
(160) |
Feb
(135) |
Mar
(98) |
Apr
(89) |
May
(115) |
Jun
(95) |
Jul
(188) |
Aug
(167) |
Sep
(153) |
Oct
(84) |
Nov
(82) |
Dec
(85) |
| 2009 |
Jan
(139) |
Feb
(133) |
Mar
(128) |
Apr
(105) |
May
(135) |
Jun
(79) |
Jul
(92) |
Aug
(134) |
Sep
(73) |
Oct
(112) |
Nov
(159) |
Dec
(80) |
| 2010 |
Jan
(100) |
Feb
(116) |
Mar
(130) |
Apr
(59) |
May
(88) |
Jun
(59) |
Jul
(69) |
Aug
(67) |
Sep
(82) |
Oct
(76) |
Nov
(59) |
Dec
(34) |
| 2011 |
Jan
(84) |
Feb
(74) |
Mar
(81) |
Apr
(94) |
May
(188) |
Jun
(72) |
Jul
(118) |
Aug
(109) |
Sep
(111) |
Oct
(80) |
Nov
(51) |
Dec
(44) |
| 2012 |
Jan
(80) |
Feb
(123) |
Mar
(46) |
Apr
(12) |
May
(40) |
Jun
(62) |
Jul
(95) |
Aug
(66) |
Sep
(65) |
Oct
(53) |
Nov
(42) |
Dec
(60) |
| 2013 |
Jan
(96) |
Feb
(96) |
Mar
(108) |
Apr
(72) |
May
(115) |
Jun
(111) |
Jul
(114) |
Aug
(87) |
Sep
(93) |
Oct
(97) |
Nov
(104) |
Dec
(82) |
| 2014 |
Jan
(96) |
Feb
(77) |
Mar
(71) |
Apr
(40) |
May
(48) |
Jun
(78) |
Jul
(54) |
Aug
(44) |
Sep
(58) |
Oct
(79) |
Nov
(51) |
Dec
(52) |
| 2015 |
Jan
(55) |
Feb
(59) |
Mar
(48) |
Apr
(40) |
May
(45) |
Jun
(63) |
Jul
(36) |
Aug
(49) |
Sep
(35) |
Oct
(58) |
Nov
(21) |
Dec
(47) |
| 2016 |
Jan
(35) |
Feb
(81) |
Mar
(43) |
Apr
(41) |
May
(77) |
Jun
(52) |
Jul
(39) |
Aug
(34) |
Sep
(107) |
Oct
(67) |
Nov
(54) |
Dec
(20) |
| 2017 |
Jan
(99) |
Feb
(37) |
Mar
(86) |
Apr
(47) |
May
(57) |
Jun
(55) |
Jul
(34) |
Aug
(31) |
Sep
(16) |
Oct
(49) |
Nov
(53) |
Dec
(33) |
| 2018 |
Jan
(25) |
Feb
(11) |
Mar
(79) |
Apr
(77) |
May
(5) |
Jun
(19) |
Jul
(17) |
Aug
(7) |
Sep
(13) |
Oct
(22) |
Nov
(13) |
Dec
(68) |
| 2019 |
Jan
(44) |
Feb
(17) |
Mar
(40) |
Apr
(39) |
May
(18) |
Jun
(14) |
Jul
(20) |
Aug
(31) |
Sep
(11) |
Oct
(35) |
Nov
(3) |
Dec
(10) |
| 2020 |
Jan
(32) |
Feb
(16) |
Mar
(10) |
Apr
(22) |
May
(2) |
Jun
(34) |
Jul
(1) |
Aug
(8) |
Sep
(36) |
Oct
(16) |
Nov
(13) |
Dec
(10) |
| 2021 |
Jan
(16) |
Feb
(23) |
Mar
(45) |
Apr
(28) |
May
(6) |
Jun
(17) |
Jul
(8) |
Aug
(1) |
Sep
(2) |
Oct
(35) |
Nov
|
Dec
(5) |
| 2022 |
Jan
|
Feb
(17) |
Mar
(23) |
Apr
(23) |
May
(9) |
Jun
(8) |
Jul
|
Aug
|
Sep
(7) |
Oct
(5) |
Nov
(16) |
Dec
(4) |
| 2023 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
(1) |
Jun
(4) |
Jul
(1) |
Aug
|
Sep
(2) |
Oct
(1) |
Nov
|
Dec
|
| 2024 |
Jan
(7) |
Feb
(13) |
Mar
(18) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(1) |
Nov
(5) |
Dec
(3) |
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
(12) |
May
(12) |
Jun
(2) |
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Ivan R. <iv...@we...> - 2004-04-04 11:17:55
|
> So the only way I could get this to work is to comment the above code and > recompile suexec. Obviously this is probably a bad idea but I just did it > to prove the point. > > Any ideas on how to make this work without hacking suexec? I will try to modify mod_security tomorrow to make it work with suexec. Perhaps I can chdir to the folder first and just use the name of the script for execution. Suexec checks the DOC_ROOT anyway. > Also, are there environment varibles I can use to get more specific in my > alers? Normally you will get MOD_SECURITY_EXECUTED, MOD_SECURITY_STATUS, and MOD_SECURITY_MESSAGE but, having just looked at the code it seems that the latter two are not available when external binaries are executed. I'll fix that in the next release. -- ModSecurity (http://www.modsecurity.org) [ Open source IDS for Web applications ] |
|
From: Mark <ad...@as...> - 2004-04-04 11:04:54
|
Jeremy Hansen wrote:
>>> So yes...this actually leads to something:
>>>
>>> [2004-04-03 10:23:15]: error: invalid command
>>> (/usr/webservers/httpd/conf/report-attack.sh)
>>>
>>> but I'm not sure exactly what it means by invalid command.
>>
>> So looking at the code:
>>
>> if ((cmd[0] == '/') || (!strncmp(cmd, "../", 3))
>> || (strstr(cmd, "/../") != NULL)) {
>> log_err("error: invalid command (%s)\n", cmd);
>> exit(104);
>> }
>>
>> so, because the line starts with a /, suexec says it's an invalid
>> command. What's the work around for this?
>
> So the only way I could get this to work is to comment the above code
> and recompile suexec. Obviously this is probably a bad idea but I
> just did it to prove the point.
>
> Any ideas on how to make this work without hacking suexec?
Personally, I would just get rid of suEXEC altogether. suEXEC requires that
the directory of your program be within the Apache webspace. And in my
experience (and yours, it seems), scripts like the one above are exactly
what you do NOT want in the web-tree. But apart from that,
Why not just hardlink (not symlink!) to it, from with your web-root space?
Then in, say,
/usr/webservers/httpd/vhosts/myhost/htdocs/
You would do:
"ln /usr/webservers/httpd/conf/report-attack.sh report-attack.sh"
So you can run a relative call to report-attack.sh, from within the Apache
webspace. Not pretty, perhaps; but it might do the trick.
P.S. I am myself rather charmed with mod_security's SecChrootDir command, as
it makes chrooting Apache rather trivial. Do that, and the need for using
suEXEC may subside even more.
Cheers,
- Mark
System Administrator Asarian-host.org
---
"If you were supposed to understand it,
we wouldn't call it code." - FedEx
|
|
From: Jeremy H. <je...@me...> - 2004-04-04 00:25:46
|
On Sat, 3 Apr 2004, Jeremy Hansen wrote:
> On Sat, 3 Apr 2004, Jeremy Hansen wrote:
>
> > On Sat, 3 Apr 2004, Ivan Ristic wrote:
> >
> > >
> > > > So I tried 1.7.6 and still, no message so I'm obviously doing something
> > > > wrong in my config. Any clues?
> > >
> > > Your script works for me without modification. One thing to try
> > > would be to use absolute paths for all binares (hostname and mail).
> > >
> > > Are you using suexec on your web server? Look in the suexec log
> > > if you are, there may be clues there.
> >
> > So yes...this actually leads to something:
> >
> > [2004-04-03 10:23:15]: error: invalid command
> > (/usr/webservers/httpd/conf/report-attack.sh)
> >
> > but I'm not sure exactly what it means by invalid command.
>
> So looking at the code:
>
> if ((cmd[0] == '/') || (!strncmp(cmd, "../", 3))
> || (strstr(cmd, "/../") != NULL)) {
> log_err("error: invalid command (%s)\n", cmd);
> exit(104);
> }
>
> so, because the line starts with a /, suexec says it's an invalid command.
> What's the work around for this?
So the only way I could get this to work is to comment the above code and
recompile suexec. Obviously this is probably a bad idea but I just did it
to prove the point.
Any ideas on how to make this work without hacking suexec?
Also, are there environment varibles I can use to get more specific in my
alers?
Thanks again
-jeremy
> Thanks
> -jeremy
>
> > Thanks
> > -jeremy
> >
> >
>
>
|
|
From: Jeremy H. <je...@me...> - 2004-04-03 18:39:59
|
On Sat, 3 Apr 2004, Jeremy Hansen wrote:
> On Sat, 3 Apr 2004, Ivan Ristic wrote:
>
> >
> > > So I tried 1.7.6 and still, no message so I'm obviously doing something
> > > wrong in my config. Any clues?
> >
> > Your script works for me without modification. One thing to try
> > would be to use absolute paths for all binares (hostname and mail).
> >
> > Are you using suexec on your web server? Look in the suexec log
> > if you are, there may be clues there.
>
> So yes...this actually leads to something:
>
> [2004-04-03 10:23:15]: error: invalid command
> (/usr/webservers/httpd/conf/report-attack.sh)
>
> but I'm not sure exactly what it means by invalid command.
So looking at the code:
if ((cmd[0] == '/') || (!strncmp(cmd, "../", 3))
|| (strstr(cmd, "/../") != NULL)) {
log_err("error: invalid command (%s)\n", cmd);
exit(104);
}
so, because the line starts with a /, suexec says it's an invalid command.
What's the work around for this?
Thanks
-jeremy
> Thanks
> -jeremy
>
>
|
|
From: Jeremy H. <je...@me...> - 2004-04-03 18:24:44
|
On Sat, 3 Apr 2004, Ivan Ristic wrote: > > > So I tried 1.7.6 and still, no message so I'm obviously doing something > > wrong in my config. Any clues? > > Your script works for me without modification. One thing to try > would be to use absolute paths for all binares (hostname and mail). > > Are you using suexec on your web server? Look in the suexec log > if you are, there may be clues there. So yes...this actually leads to something: [2004-04-03 10:23:15]: error: invalid command (/usr/webservers/httpd/conf/report-attack.sh) but I'm not sure exactly what it means by invalid command. Thanks -jeremy |
|
From: Ivan R. <iv...@we...> - 2004-04-03 17:14:02
|
> So I tried 1.7.6 and still, no message so I'm obviously doing something > wrong in my config. Any clues? Your script works for me without modification. One thing to try would be to use absolute paths for all binares (hostname and mail). Are you using suexec on your web server? Look in the suexec log if you are, there may be clues there. -- ModSecurity (http://www.modsecurity.org) [ Open source IDS for Web applications ] |
|
From: Jeremy H. <je...@me...> - 2004-04-03 16:33:07
|
On Sat, 3 Apr 2004, Ulf Harnhammar wrote: > > But I don't receive the email, yet, when I execute this from the command > > line, I get the email no problem. > > > > #!/bin/sh > > > > > > HOSTNAME=`hostname` > > > > > > > > > echo "Attack detected. Check audit log" | mail -s "$HOSTNAME: attack > > > detected" in...@me... > > A guess would be some problem with $PATH. Try inserting export PATH=/bin:/usr/bin or something similar as the second line of your script. So I tried 1.7.6 and still, no message so I'm obviously doing something wrong in my config. Any clues? Thanks -jeremy > // Ulf Harnhammar > http://www.advogato.org/person/metaur > > |
|
From: Jeremy H. <je...@me...> - 2004-04-03 16:07:44
|
On Sat, 3 Apr 2004, Ulf Harnhammar wrote: > > But I don't receive the email, yet, when I execute this from the command > > line, I get the email no problem. > > > > #!/bin/sh > > > > > > HOSTNAME=`hostname` > > > > > > > > > echo "Attack detected. Check audit log" | mail -s "$HOSTNAME: attack > > > detected" in...@me... > > A guess would be some problem with $PATH. Try inserting export > PATH=/bin:/usr/bin or something similar as the second line of your > script. I thought about this as well and tried it. Still no message. I'm also watching the mail server logs and I don't ever see a delivery attempt even. I'm going to try the "stable" release today. Perhaps this just isn't working in the 1.8 beta. -jeremy > // Ulf Harnhammar > http://www.advogato.org/person/metaur > > |
|
From: Ulf H. <me...@op...> - 2004-04-03 13:15:55
|
> But I don't receive the email, yet, when I execute this from the command > line, I get the email no problem. > > #!/bin/sh > > > > HOSTNAME=`hostname` > > > > > > echo "Attack detected. Check audit log" | mail -s "$HOSTNAME: attack > > detected" in...@me... A guess would be some problem with $PATH. Try inserting export PATH=/bin:/usr/bin or something similar as the second line of your script. // Ulf Harnhammar http://www.advogato.org/person/metaur -- _____________________________________________________________ Web-based SMS services available at http://www.operamail.com. From your mailbox to local or overseas cell phones. Powered by Outblaze |
|
From: Jeremy H. <je...@me...> - 2004-04-03 05:09:53
|
So I quoted it this time: SecFilter /etc/passwd "log,exec:/usr/webservers/httpd/conf/report-attack.sh" and I see this in the audit log: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030922 mod_security-executed: /usr/webservers/httpd/conf/report-attack.sh But I don't receive the email, yet, when I execute this from the command line, I get the email no problem. Thanks -jeremy On Fri, 2 Apr 2004, Jeremy Hansen wrote: > > I'm using version mod_security-1.8dev1.tar.gz and I can't seem to get > notification working. Here my rules: > > # Execute the external script on filter match > SecFilter yyy log,exec:/usr/webservers/httpd/conf/report-attack.sh > > and here's the little shell script: > > #!/bin/sh > > HOSTNAME=`hostname` > > > echo "Attack detected. Check audit log" | mail -s "$HOSTNAME: attack > detected" in...@me... > > just simple script. Using the test suite, I definitely am tripping some > filters... > > Test "38 Unicode test 1": OK > Test "39 Unicode test 2": OK > Test "40 Unicode test 3": OK > Test "43 post range check bug": OK > Test "44 normalisation bug": OK > Test "45 null byte attack": OK > Test "43 multipart/form-data test": OK > Test "53 named cookie test": OK > > etc.. > > but nothing in my email... > > Very new to this so perhaps my rules are completely wrong. Here's the > full rules list: > > # Turn the filtering engine On or Off > SecFilterEngine On > > # The audit engine works independently and > # can be turned On of Off on the per-server or > # on the per-directory basis > SecAuditEngine RelevantOnly > > # The name of the audit log file > SecAuditLog /var/log/httpd/logs/audit_log > > # Should mod_security inspect POST payloads > SecFilterScanPOST On > > # Check URL encoding > SecFilterCheckURLEncoding On > > # Default action set > SecFilterDefaultAction "deny,log,status:500" > > # Only allow certain byte values to be a part of the request. > # This is pretty relaxed, most applications where only English > # is used will happily work with a range 32 - 126. > SecFilterForceByteRange 32 126 > > # Only accept request encodings we know how to handle > # SecFilterSelective HTTP_Content-Type > "!^(|application/x-www-form-urlencoded|multipart/form-data)$" > > # Don't accept transfer encodings we know we don't handle > # (and you don't need it anyway) > SecFilterSelective HTTP_Transfer-Encoding "!^$" > > # Simple example filter > # SecFilter 111 > > # Chroot > # SecChrootDir /usr/webservers/httpd > > # Change Signature > SecServerSignature "FuckYouVeryMuch/2.0" > > # Command execution attacks > SecFilter /etc/passwd > SecFilter /etc/shadow > SecFilter /etc/password > SecFilter /bin/ls > # Directory traversal attacks > SecFilter "\.\./" > # XSS attacks > SecFilter "<(.|\n)+>" > SecFilter "<[[:space:]]*script" > > # SQL injection attacks > SecFilter "delete[[:space:]]+from" > SecFilter "insert[[:space:]]+into" > SecFilter "select.+from" > > SecFilterSelective ARG_b2inc "!^$" > > SecFilterSelective ARG_PHPSESSID "!^[0-9a-z]*$" > SecFilterSelective COOKIE_PHPSESSID "!^[0-9a-z]*$" > > <Location /cgi-bin/FormMail> > SecFilterSelective "ARG_recipient" "!@methanesea\.com$" > </Location> > > SecFilterSelective OUTPUT "Fatal error:" > > # Execute the external script on filter match > SecFilter yyy log,exec:/usr/webservers/httpd/conf/report-attack.sh > > # Redirect user on filter match > SecFilter xxx redirect:http://www.methanesea.com > > # SecFilterDebugLog /var/log/httpd/logs/modsec_debug_log > # SecFilterDebugLevel 100 > > # Simple filter > SecFilter 111 > > # Only check the QUERY_STRING variable > SecFilterSelective QUERY_STRING 222 > > # Only check the body of the POST request > SecFilterSelective POST_PAYLOAD 333 > > # Only check arguments (will work for GET and POST) > SecFilterSelective ARGS 444 > > # Another test filter, will be denied with 404 but not logged > # action supplied as a parameter overrides the default action > SecFilter 999 "deny,nolog,status:500" > > Mostly stolen from various articles and docs. > > Thanks for any tips. > -jeremy > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > mod-security-users mailing list > mod...@li... > https://lists.sourceforge.net/lists/listinfo/mod-security-users > |
|
From: Jeremy H. <je...@me...> - 2004-04-03 04:50:48
|
I'm using version mod_security-1.8dev1.tar.gz and I can't seem to get
notification working. Here my rules:
# Execute the external script on filter match
SecFilter yyy log,exec:/usr/webservers/httpd/conf/report-attack.sh
and here's the little shell script:
#!/bin/sh
HOSTNAME=`hostname`
echo "Attack detected. Check audit log" | mail -s "$HOSTNAME: attack
detected" in...@me...
just simple script. Using the test suite, I definitely am tripping some
filters...
Test "38 Unicode test 1": OK
Test "39 Unicode test 2": OK
Test "40 Unicode test 3": OK
Test "43 post range check bug": OK
Test "44 normalisation bug": OK
Test "45 null byte attack": OK
Test "43 multipart/form-data test": OK
Test "53 named cookie test": OK
etc..
but nothing in my email...
Very new to this so perhaps my rules are completely wrong. Here's the
full rules list:
# Turn the filtering engine On or Off
SecFilterEngine On
# The audit engine works independently and
# can be turned On of Off on the per-server or
# on the per-directory basis
SecAuditEngine RelevantOnly
# The name of the audit log file
SecAuditLog /var/log/httpd/logs/audit_log
# Should mod_security inspect POST payloads
SecFilterScanPOST On
# Check URL encoding
SecFilterCheckURLEncoding On
# Default action set
SecFilterDefaultAction "deny,log,status:500"
# Only allow certain byte values to be a part of the request.
# This is pretty relaxed, most applications where only English
# is used will happily work with a range 32 - 126.
SecFilterForceByteRange 32 126
# Only accept request encodings we know how to handle
# SecFilterSelective HTTP_Content-Type
"!^(|application/x-www-form-urlencoded|multipart/form-data)$"
# Don't accept transfer encodings we know we don't handle
# (and you don't need it anyway)
SecFilterSelective HTTP_Transfer-Encoding "!^$"
# Simple example filter
# SecFilter 111
# Chroot
# SecChrootDir /usr/webservers/httpd
# Change Signature
SecServerSignature "FuckYouVeryMuch/2.0"
# Command execution attacks
SecFilter /etc/passwd
SecFilter /etc/shadow
SecFilter /etc/password
SecFilter /bin/ls
# Directory traversal attacks
SecFilter "\.\./"
# XSS attacks
SecFilter "<(.|\n)+>"
SecFilter "<[[:space:]]*script"
# SQL injection attacks
SecFilter "delete[[:space:]]+from"
SecFilter "insert[[:space:]]+into"
SecFilter "select.+from"
SecFilterSelective ARG_b2inc "!^$"
SecFilterSelective ARG_PHPSESSID "!^[0-9a-z]*$"
SecFilterSelective COOKIE_PHPSESSID "!^[0-9a-z]*$"
<Location /cgi-bin/FormMail>
SecFilterSelective "ARG_recipient" "!@methanesea\.com$"
</Location>
SecFilterSelective OUTPUT "Fatal error:"
# Execute the external script on filter match
SecFilter yyy log,exec:/usr/webservers/httpd/conf/report-attack.sh
# Redirect user on filter match
SecFilter xxx redirect:http://www.methanesea.com
# SecFilterDebugLog /var/log/httpd/logs/modsec_debug_log
# SecFilterDebugLevel 100
# Simple filter
SecFilter 111
# Only check the QUERY_STRING variable
SecFilterSelective QUERY_STRING 222
# Only check the body of the POST request
SecFilterSelective POST_PAYLOAD 333
# Only check arguments (will work for GET and POST)
SecFilterSelective ARGS 444
# Another test filter, will be denied with 404 but not logged
# action supplied as a parameter overrides the default action
SecFilter 999 "deny,nolog,status:500"
Mostly stolen from various articles and docs.
Thanks for any tips.
-jeremy
|
|
From: Ivan R. <iv...@we...> - 2004-03-31 22:05:14
|
L. Christopher Luther wrote: > OK, I guess no one has made any LogWatch configurations > to work with mod_security. So I guess the next question > is what are people using to monitor the mod_security logs? > IS anyone actually monitoring the mod_security logs? I have found the artificial ignorance concept to be very useful: http://archives.neohapsis.com/archives/nfr-wizards/1997/09/0098.html -- ModSecurity (http://www.modsecurity.org) [ Open source IDS for Web applications ] |
|
From: Jim H. <jim...@rc...> - 2004-03-31 21:14:05
|
Christopher, I user Big Brother to monitor my mod_security logfile, it works like a champ. I have tested it on several occassion with NESSUS and it works great. Regards, Jim ---- Original message ---- >Date: Wed, 31 Mar 2004 15:52:08 -0500 >From: "L. Christopher Luther" <CL...@Xy...> >Subject: RE: [mod-security-users] LogWatch Filter and Config >To: "ModSecurity-Users \(E-mail\)" <mod-security- us...@li...> > > OK, I guess no one has made any LogWatch > configurations to work with mod_security. So I > guess the next question is what are people using to > monitor the mod_security logs? IS anyone actually > monitoring the mod_security logs? > > TIA > > -----Original Message----- > From: > mod...@li... > [mailto:mod...@li...] On > Behalf Of L. Christopher Luther > Sent: Tuesday, March 23, 2004 7:20 PM > To: ModSecurity-Users (E-mail) > Subject: [mod-security-users] LogWatch Filter and > Config > Sensitivity: Confidential > > Has anyone created a LogWatch config file and > filter for mod_security's audit log? > > Sincerely, > > L. Christopher Luther > Technical Consultant > Xybernaut Solutions, Inc. > (703) 654-3642 > cl...@xy... > PGP Public KeyID: 0x21261B88 > http://www.xybernautsolutions.com > > CONFIDENTIALITY NOTE: This communication contains > information that is confidential and/or legally > privileged. > This information is intended only for the use of > the individual > or entity named on this communication. If you are > not the > intended recipient, you are hereby notified that > any disclosure, > copying, distribution, printing or other use of, > or any action > in reliance on, the contents of this communication > is strictly > prohibited. If you receive this communication in > error, please > immediately notify us by telephone at (703) > 631-6925. > > ============================================ > Unsolicited commercial e-mail will automatically > be > reported to the appropriate abuse@ - without > exception. > ============================================ > > CONFIDENTIALITY NOTE: This communication contains > information that is confidential and/or legally > privileged. This information is intended only for > the use of the individual or entity named on this > communication. If you are not the intended > recipient, you are hereby notified that any > disclosure, copying, distribution, printing or > other use of, or any action in reliance on, the > contents of this communication is strictly > prohibited. If you received this communication in > error, please immediately notify us by telephone > at (703) 631-6925. |
|
From: L. C. L. <CL...@Xy...> - 2004-03-31 20:52:24
|
OK, I guess no one has made any LogWatch configurations to work with = mod_security. So I guess the next question is what are people using to = monitor the mod_security logs? IS anyone actually monitoring the = mod_security logs? =20 =20 TIA -----Original Message----- From: mod...@li... = [mailto:mod...@li...]On Behalf Of L. = Christopher Luther Sent: Tuesday, March 23, 2004 7:20 PM To: ModSecurity-Users (E-mail) Subject: [mod-security-users] LogWatch Filter and Config Sensitivity: Confidential Has anyone created a LogWatch config file and filter for mod_security's = audit log?=20 Sincerely, =20 L. Christopher Luther =20 Technical Consultant =20 Xybernaut Solutions, Inc. =20 (703) 654-3642 =20 cl...@xy... =20 PGP Public KeyID: 0x21261B88=20 http://www.xybernautsolutions.com =20 CONFIDENTIALITY NOTE: This communication contains=20 information that is confidential and/or legally privileged. =20 This information is intended only for the use of the individual=20 or entity named on this communication. If you are not the=20 intended recipient, you are hereby notified that any disclosure,=20 copying, distribution, printing or other use of, or any action=20 in reliance on, the contents of this communication is strictly=20 prohibited. If you receive this communication in error, please=20 immediately notify us by telephone at (703) 631-6925.=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Unsolicited commercial e-mail will automatically be reported to the appropriate abuse@ - without exception. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=20 CONFIDENTIALITY NOTE: This communication contains information that is = confidential and/or legally privileged. This information is intended = only for the use of the individual or entity named on this = communication. If you are not the intended recipient, you are hereby = notified that any disclosure, copying, distribution, printing or other = use of, or any action in reliance on, the contents of this communication = is strictly prohibited. If you received this communication in error, = please immediately notify us by telephone at (703) 631-6925. |
|
From: Ivan R. <iv...@we...> - 2004-03-31 20:22:27
|
> However, I am having difficulties capturing these Webdav > exploits before Apache sends a 414 error response. Those > "SEARCH" request methods are slipping by mod_security. > > ... > > Anyone having success at capturing Webdav exploits > using mod_security? I am sure there is something > I am overlooking in my configuration. I don't have the time to check right now but I'm pretty sure Apache rejects the request before mod_security gets to look at it. The same happens with TRACE. There's no way around it at the moment. I think you should be able to use mod_rewrite to detect and reject that request. -- ModSecurity (http://www.modsecurity.org) [ Open source IDS for Web applications ] |
|
From: Purl G. <pur...@pu...> - 2004-03-30 18:23:55
|
Many of you have noticed Apache log entries for
this idiotic Webdav exploit which are extremely
long and generate a "URI too long" error response.
An example which is truncated:
66.215.211.96 66.215.211.96 [30/Mar/2004:09:48:40 -0800] "SEARCH /\x90
This request method "SEARCH" is not recognized by
Apache 1.3.x series and presents a problem.
I enjoy very good success loading and running mod_security
for my Apache server. Ran the enclosed tests, all seems to
be working perfectly. Very nice module, indeed.
However, I am having difficulties capturing these Webdav
exploits before Apache sends a 414 error response. Those
"SEARCH" request methods are slipping by mod_security.
Currently I am trying this entry for mod_security:
# Kill Search Request Method
SecFilterSelective "REQUEST_METHOD" "^.*SEARCH.*$"
I have tried variations on this, tried a simple filter,
but cannot capture those darn Webdav exploits. My return
error message should be a 405 method not allowed but
have yet to succeed at this.
Anyone having success at capturing Webdav exploits
using mod_security? I am sure there is something
I am overlooking in my configuration.
Both your comments and help are appreciated.
Thanks,
Kira
|
|
From: L. C. L. <CL...@Xy...> - 2004-03-24 00:19:46
|
Has anyone created a LogWatch config file and filter for mod_security's = audit log? Sincerely, =20 L. Christopher Luther =20 Technical Consultant =20 Xybernaut Solutions, Inc. =20 (703) 654-3642 =20 cl...@xy... =20 PGP Public KeyID: 0x21261B88 http://www.xybernautsolutions.com =20 CONFIDENTIALITY NOTE: This communication contains=20 information that is confidential and/or legally privileged. =20 This information is intended only for the use of the individual=20 or entity named on this communication. If you are not the=20 intended recipient, you are hereby notified that any disclosure,=20 copying, distribution, printing or other use of, or any action=20 in reliance on, the contents of this communication is strictly=20 prohibited. If you receive this communication in error, please=20 immediately notify us by telephone at (703) 631-6925.=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Unsolicited commercial e-mail will automatically be=20 reported to the appropriate abuse@ - without exception. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D CONFIDENTIALITY NOTE: This communication contains information that is = confidential and/or legally privileged. This information is intended = only for the use of the individual or entity named on this = communication. If you are not the intended recipient, you are hereby = notified that any disclosure, copying, distribution, printing or other = use of, or any action in reliance on, the contents of this communication = is strictly prohibited. If you received this communication in error, = please immediately notify us by telephone at (703) 631-6925. |
|
From: Jochen B. <jo...@ro...> - 2004-03-23 16:20:36
|
Hi! Today I have installed a debian/woody box with Apache 1.3.26 and have made a debian package of mod-security 1.7.6. I give no guarantee that the packages work properly, because they were only created for my own use. If you are interested you can download the packages at www.roastbyte.net/debs.html Have fun. best regards Jochen |
|
From: Ivan R. <iv...@we...> - 2004-03-22 16:14:27
|
> I am using mod_security 1.7.6 with Apache 2.0.49 on Solaris 8 with > OpenSSL 0.9.7d > When a pdf file is uploaded it makes the Apache child process > crashes. Here's what I get: > [Mon Mar 22 13:59:52 2004] [notice] child pid 827 exit signal Segmentation > fault (11) > > > When I disable the security rules the file upload works fine. It does not crash when you disable the rules but leave "SecFilterScanPOST On"? I am uploading a 3.6 MB file on Apache 2.0.49 + mod_security 1.7.6 on Linux (sorry, I don't have access to a Solaris box) without any problems, with a match or without it. I will try to add mod_ssl to the mix but that shouldn't make any difference. Did you compile Apache yourself? Is the Apache using the built-in regular expression library? Or the Solaris implementation? > I think that filtering makes the process crash maybe because the file > is too big ( 1,5 MBytes). The security rules are very simple ( here's a few): > SecFilterScanPOST On > SecFilterCheckURLEncoding On > SecFilter "delete[[:space:]]+from" > SecFilter "insert[[:space:]]+into" > SecFilter "select.+from" Can you post the PDF file somewhere (for me)? Maybe there's something in it that crashes the regular expression library. > Since, it's a production system I can't do very more tests. > How could I disable scanning of an uploaded file by mod_security engine ? > > Would that rule : > SecFilterSelective "HTTP_CONTENT_TYPE" multipart/form-data allow > at the beginning of the rules list be sufficient ? That should work, provided it does not crash with "SecFilterScanPOST On" but only when a regular expression is processed. Else, use "SecFilterScanPOST On". Other things you could do: Set the debug level to 9, "SecFilterDebugLevel 9", make it crash and send me the debug file. -- ModSecurity (http://www.modsecurity.org) [ Open source IDS for Web applications ] |
|
From: <lde...@ne...> - 2004-03-22 15:00:24
|
Hi, I am using mod_security 1.7.6 with Apache 2.0.49 on Solaris 8 with OpenSSL 0.9.7d When a pdf file is uploaded it makes the Apache child process crashes. Here's what I get: [Mon Mar 22 13:59:52 2004] [notice] child pid 827 exit signal Segmentatio= n fault (11) When I disable the security rules the file upload works fine. I think that filtering makes the process crash maybe because the file is too big ( 1,5 MBytes). The security rules are very simple ( here's a f= ew): SecFilterScanPOST On SecFilterCheckURLEncoding On SecFilter "delete[[:space:]]+from" SecFilter "insert[[:space:]]+into" SecFilter "select.+from" I didn't enable the SecFilterForceByteRange rule. The file is uploaded via a HTTP POST request Since, it's a production system I can't do very more tests. How could I disable scanning of an uploaded file by mod_security engine ? Would that rule : SecFilterSelective "HTTP_CONTENT_TYPE" multipart/form-data allow at the beginning of the rules list be sufficient ? Thanks, Luc |
|
From: Mike P. <mpl...@am...> - 2004-03-22 01:31:58
|
On Sunday 21 March 2004 7:47 pm, Ivan Ristic wrote: > > Thanks for the reply and you are correct I do not have ServerTokens set > > to full. In fact, I do not even have ServerTokens in the configuration > > file at all. > > Then you do, the default value for that directive is Full. > > > Here is my httpd.conf file as you requested. Although, I am still > > confused as to why nothing is being logged when I tell it to. > > > > Thanks for the help and thanks for creating this module. > > You are welcome. > > > ------------------------------ File below ------------------- > > > > ## > > ## httpd.conf -- Apache HTTP server configuration file > > ## > > > > ... > > > > <IfModule mod_securtiy.c> > > ^^^^ > You have a typo here, that's why the module does not > get loaded :) Thanks for pointing that out. :) -- Mike Plemmons mpl...@am... |
|
From: Ivan R. <iv...@we...> - 2004-03-22 00:45:28
|
> Thanks for the reply and you are correct I do not have ServerTokens set to
> full. In fact, I do not even have ServerTokens in the configuration file at
> all.
Then you do, the default value for that directive is Full.
> Here is my httpd.conf file as you requested. Although, I am still
> confused as to why nothing is being logged when I tell it to.
>
> Thanks for the help and thanks for creating this module.
You are welcome.
> ------------------------------ File below -------------------
>
> ##
> ## httpd.conf -- Apache HTTP server configuration file
> ##
>
> ...
>
> <IfModule mod_securtiy.c>
^^^^
You have a typo here, that's why the module does not
get loaded :)
--
ModSecurity (http://www.modsecurity.org)
[ Open source IDS for Web applications ]
|
|
From: Ivan R. <iv...@we...> - 2004-03-21 22:27:59
|
Mike Plemmons wrote: > Hello, > I am running version 1.7.6 with Apache 1.3.29 on a Slackware -current > machine. I am using a Slackware package so I did not compile it. I > installed mod_security using the apxs -cia command but I am having problems. > > I have the module loading, or so I think I do, and I have the mod_security.c > configuration added at the very bottom of my httpd.conf file. From what I > can tell mod_security is not actualy running. No log files are being created > even though I have specfically given them an absolute path to the same place > the apache log files are. I have SecServerResponseToken set to On and when I > run a GET request from a telnet session I do not see mod_security listed. > > What other steps do I need to do in order to get mod_security to work? What you did normally works for me. Only one line is required to load the module: LoadModule security_module /usr/lib/apache/mod_security.so But if there is a "ClearModuleDirective" somewhere in the configuration file you will also need to add: AddModule mod_security.c After that, all you need is the module configuration. Send me your httpd.conf (and other files if you have your configuration distributed) and I'll look at it. The fact that the server started without complaining about the SecServerResponse directive means mod_security is active. About the tokens missing in the server signature - maybe you don't have ServerTokens set to Full? -- ModSecurity (http://www.modsecurity.org) [ Open source IDS for Web applications ] |
|
From: Mike P. <mpl...@am...> - 2004-03-21 21:49:12
|
Hello, I am running version 1.7.6 with Apache 1.3.29 on a Slackware -current machine. I am using a Slackware package so I did not compile it. I installed mod_security using the apxs -cia command but I am having problems. I have the module loading, or so I think I do, and I have the mod_security.c configuration added at the very bottom of my httpd.conf file. From what I can tell mod_security is not actualy running. No log files are being created even though I have specfically given them an absolute path to the same place the apache log files are. I have SecServerResponseToken set to On and when I run a GET request from a telnet session I do not see mod_security listed. What other steps do I need to do in order to get mod_security to work? Thanks in advance, -- Mike Plemmons mpl...@am... |
|
From: Jim H. <jim...@rc...> - 2004-03-19 01:30:14
|
I would say go for Apache 2.0.48, with the addition of mod_security you can chroot the server very easily. If you are talking a heavily loaded system and want it really secure, chroot the server. Regards, Jim -----Original Message----- From: mod...@li... [mailto:mod...@li...] On Behalf Of deb...@sp... Sent: Thursday, March 18, 2004 11:25 AM To: mod...@li... Subject: [mod-security-users] mod-security resource usage? I am trying to spec out a system to runs as a modsec appliance providing IDS /IPS to multiple IIS websites some very heavily used Can anyone thing be figures on process load, memory usage of modsecurity? Do people recommend apache 1.3 or 2 if 2 prefork variable or other? thanks Mat ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ mod-security-users mailing list mod...@li... https://lists.sourceforge.net/lists/listinfo/mod-security-users |