I wonder if you'd get the info you want if you start the Apache instance in verbose mode, make a normal connection in your browser, then shut off the instance - you get a bunch of spooled files with all kinds of info on what was done.

You use '-vv' in the options to get verbose mode.


On 1/14/2014 4:42 PM, Steinmetz, Paul wrote:
V6R1 info center shows default is on.
V7R1 info center show default is off.
Did the default change from V6R1 to V7R1, or could there be a typo in the center.

With Windows7 , can't use the recommended TELNET test to confirm the status.

"Normally you will have this enabled by default, but if you want to test if it is really enabled on your server you just have to telnet on the port your web server is running and request for "TRACE / HTTP/1.0" if you get a positive reply it means TRACE is enabled on your system.

Any recommendations on how to confirm.

-----Original Message-----
From: Steinmetz, Paul
Sent: Tuesday, January 14, 2014 4:19 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Possible iSeries HTTP vulnerabilties TRACE and/or TRACK methods

So even if TraceEnable is not in the httpconf file, by default it is off.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Nadir Amra
Sent: Tuesday, January 14, 2014 3:35 PM
To: Midrange Systems Technical Discussion
Subject: Re: Possible iSeries HTTP vulnerabilties TRACE and/or TRACK methods

According to the InfoCenter directive reference, if not specified the default is

TraceEnable off


Nadir Amra

From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
Date: 01/14/2014 02:29 PM
Subject: Possible iSeries HTTP vulnerabilties TRACE and/or TRACK
Sent by: midrange-l-bounces@xxxxxxxxxxxx

Security audit is requesting that these vulnerabilities be disabled.
Reviewing the httpd.conf config files, I see no evidence of TRACE and/or TRACK, so I'm assuming these are on by default, and need to be disabled by one of the suggested methods.
All of our HTTP instances are Apache 2.2.11(i5).
Am I correct that I need to re-visit every HTTP instance, adding one of the two recommendations below.

To disable
TraceEnabled Off

# disable TRACE in the main scope of httpd.conf RewriteEngine On RewriteCond %{REQUEST_METHOD} ^TRACE RewriteRule .* - [F] ...
<VirtualHost www.example.com>
# disable TRACE in the www.example.com virtual host RewriteEngine On RewriteCond %{REQUEST_METHOD} ^TRACE RewriteRule .* - [F] </VirtualHost>

mod_rewrite must be active for these directives to be accepted. If mod_rewrite is not already active in your configuration:

Plugin Text: Synopsis: Debugging functions are enabled on the remote web
Description: The remote web server supports the TRACE and/or TRACK
methods. TRACE and TRACK are HTTP methods that are used to debug web
server connections.
Solution: Disable these methods. Refer to the plugin output for more
See Also:
Risk Factor: Medium
CVSS Base Score: 4.3
CVSS Temporal Score: 3.9
CVSS Temporal Vector: CVSS2#E:F/RL:W/RC:C
Plugin Output:
To disable these methods, add the following lines for each virtual
host in your configuration file :
RewriteEngine on
RewriteRule .* - [F]
Alternatively, note that Apache versions 1.3.34, 2.0.55, and 2.2
support disabling the TRACE method natively via the 'TraceEnable'
Nessus sent

Thank You
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home


This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page