Solved

server scanned hot for log4j after upgrade

  • 7 January 2022
  • 4 replies
  • 467 views

Badge +1

I upgraded my CommServ to 11_20_85 and I read that this would remediate the log4j vulnerability. So I had the IA folks rescan the server and it came back hot and this is the path they sited. E:\ProgramFiles\Commvault\ContentStore\CVCIEngine\CvPreviewHome\webapps\CvContentPreviewGenApp\WEB-INF\lib\log4j-1.2.17.jar - they are advising to upgrade to a version of Apache Log4j

icon

Best answer by Aplynx 7 January 2022, 16:11

View original

4 replies

Userlevel 6
Badge +13

Please take a look at this thread:

CVE-2021-4104: The Commvault software does not use the JMSAppender module and, therefore, the vulnerability about log4j 1.x versions does not affect any Commvault products.

Badge +1

Thanks, I’ll relay this to our IA folks

Badge +1

Out of curiosity can this jar file be deleted.

Userlevel 7
Badge +23

@Will Patrick , I wouldn't delete anything.  We likely use it for valid purposes, just not the vulnerable aspect/portion.

Reply