Brian Redd Brian Redd - 1 year ago 2328
Java Question

Can't resolve Log Forging Fortify issue

I am having trouble fixing a Log Forging issue in Fortify. The issue, "writes unvalidated user input to the log", is being raised from both of the logging calls in the getLongFromTimestamp() method.

public long getLongFromTimestamp(final String value) {"getLongFromTimestamp(" + cleanLogString(value) + ")");

long longVal = 0;
Date tempDate = null;
try {
tempDate = new SimpleDateFormat(FORMAT_YYYYMMDDHHMMSS, Locale.US).parse(value);
} catch (ParseException e) {
LOGGER.warn("Failed to convert to Date: " + cleanLogString(value) + " Exception: " + cleanLogString(e.getMessage()));
throw new Exception(e);

if (tempDate != null) {
longVal = tempDate.getTime();
return longVal;

private cleanLogString(String logString) {
String clean = logString.replaceAll("[^A-Za-z0-9]", "");

if(!logString.equals(clean)) {
clean += " (CLEANED)";

return clean;

The cleanLogString() method has fixed other Log Forging Fortify issues in my project, however it has no effect on the 2 above.

Any help would be appreciated!

Answer Source

Originally when this question was written our team was using log4j v1.2.8, however we noticed that all the log forging issues disappeared after upgrading to log4j v2.6.2.

Once the log4j version is upgraded the Fortify log forging issues should go away. The cleanLogString() method form the question above is also unnecessary. For example:"getLongFromTimestamp(" + value + ")");
Recommended from our users: Dynamic Network Monitoring from WhatsUp Gold from IPSwitch. Free Download