Win a copy of Cloud Native PatternsE this week in the Cloud forum
or Natural Language Processing in the AI/ML forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Devaka Cooray
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Bear Bibeault
Sheriffs:
  • Paul Clapham
  • Knute Snortum
  • Rob Spoor
Saloon Keepers:
  • Tim Moores
  • Ron McLeod
  • Piet Souris
  • Stephan van Hulst
  • Carey Brown
Bartenders:
  • Tim Holloway
  • Frits Walraven
  • Ganesh Patekar

"java.io. CharConversionException: isHexDigit" - Trojan Attempt?

 
Ranch Hand
Posts: 585
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm getting the error (see below) on Tomcat (it's not logged in the log file for some reason, but was reported in the command window), and I'm not sure what it's from. I fear it may be someone attempting to load a trojan on the webserver (similar to how code red worked I think). Does anyone know what it could be?

 
Ranch Hand
Posts: 3695
IntelliJ IDE Java Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I can't speak to what is causing the error aside from "malformed request", which viruses and trojans frequently make.

As for why you are getting it on your console, I tracked down the following in the code:
http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat/src/share/org/apache/tomcat/util/http/Attic/Parameters.java

in method:
org.apache.tomcat.util.http.Parameters.processParameters()

which is part of your stack trace, we find:

So that's where the stacktrace comes from (probably?); this bad-mannered code. The line numbers don't really match up, but I'm assuming I'm looking at some version of the code that is not in the 5.0.x build. Plus, it's in the Attic, with notations that the code has been moved to the connectors source. But obviously the build of Tomcat (and the connector you're using) still uses this?

You *ought* to be able to match up this exception with an access request, through your Apache web server logs, or if you're not using Apache, then through tomcat's access log (unless you've shut it off).
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!