It's all about the answers!

Ask a question

Resolution for Apache Tomcat 7 vulnerability with CLM 4.0.1


Chris Chinchiolo (8611716) | asked Dec 04 '12, 8:56 p.m.
retagged Dec 11 '12, 3:40 p.m. by Jerry Shengulette (63914)
I have just scanned a  system and was flagged with several Apache Tomcat 7 vulnerability with CLM 4.0.1.  In the past I was able to follow some directions from Rational to patch 5.5 with Apache fixes.  I would like some information on the Apache Tomcat 7 process from Rational before I apply this to over 40 consoles in production. 


High Severity Vulnerability
Apache Tomcat 7.0.x < 7.0.30 DIGEST Authentication Multiple Security Weaknesses
Synopsis :
The remote Apache Tomcat service may be affected by multiple security
weaknesses.
Description :
According to its self-reported version number, the instance of Apache
Tomcat 7.0 listening on the remote host is earlier than Tomcat 7.0.30
and, therefore, may be affected by the following vulnerabilities :

- Replay-countermeasure functionality in HTTP Digest
Access Authentication tracks cnonce values instead of
nonce values, which makes it easier for attackers to
bypass access restrictions by sniffing the network for
valid requests. (CVE-2012-5885)

- HTTP Digest Access Authentication implementation caches
information about the authenticated user, which could
potentially allow an attacker to bypass authentication
via session ID. (CVE-2012-5886)

- HTTP Digest Access Authentication implementation does
not properly check for stale nonce values with
enforcement of proper credentials, which allows an
attacker to bypass restrictions by sniffing requests.
! (CVE-2012-5887)

Note that Nessus did not actually test for the flaws but instead has
relied on the version in Tomcat's banner or error page so these may be
false positives.

See also :

http://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.30

Solution :
Update Apache Tomcat to version 7.0.30 or later.
Plugin Output :

Source : <title>Apache Tomcat/7.0.25
Installed version : 7.0.25
Fixed version : 7.0.30




Comments
Amber Rallis commented Dec 20 '12, 12:29 p.m.

Hello, I have the same issue with my Rational server. Is there a way to update the Apache to 7.0.30 or later?

2 answers



permanent link
Chris Chinchiolo (8611716) | answered Jan 02 '13, 6:51 p.m.
I have satisfied the issues.........

1.  Download the Tomcat core zip file from its download site
             http://tomcat.apache.org/download-70.cgi
             apache-tomcat-7.0.34.zip
2.  Extract and delete the extracted directories
      Delete (logs)
      Delete (temp)
      Delete (webapps)
      Delete (work)
      Remove files (LICENSE.txt, NOTICE.txt, RELEASE-NOTES.txt and RUNNING.txt)
      And Remove the apache-tomcat-7.0.34\conf\server.xml (file so you do not over wright the current one when replacing)

3.  Make a complete copy of JazzTeamServerInstall\server\tomcat
4.  Copy the remaining directories from below and replace out of box tomcat
         Copy apache-tomcat-7.0.34\bin  (Replace JazzTeamServerInstall\server\tomcat\bin)
         Copy apache-tomcat-7.0.34\conf  (Replace JazzTeamServerInstall\server\tomcat\conf)
         Copy apache-tomcat-7.0.34\lib  (Replace JazzTeamServerInstall\server\tomcat\lib)
5 Start Console in foreground to verify no issues

I have had running on over 20 consoles with no issues and scan comes back with no issues.....


permanent link
Martha (Ruby) Andrews (3.0k44051) | answered Dec 26 '12, 6:51 p.m.
JAZZ DEVELOPER
edited Dec 26 '12, 6:51 p.m.
Hello,
Take a look at http://www-01.ibm.com/support/docview.wss?uid=swg21448666 . The tech note talks about an older version of Tomcat and CLM, but should work for Tomcat 7.0, too:

When editing the server.xml file, use the settings in step 8b (or copy the entire Connector port="9443" element from the server.xml that you backed up in step 1).

I have not tested this myself.

Martha (Ruby) Andrews
Jazz L3 Developer

Your answer


Register or to post your answer.