Vulnerability Remediation

Lingoport's Response to Major Software Vulnerabilities

Apache Log4j Security Vulnerabilities

A major security vulnerability allowing for remote code execution on affected systems.

See: https://logging.apache.org/log4j/2.x/security.html

Lingoport Response

Pending further action, Lingoport has shut down all non-critical systems.

Critical systems have been patched to remove all copies of log4j 2.x with log4j 2.16 followed by a hard reboot.

For Lingoport Clients

The below scripts may be used in conjunction to replace all log4j 2.x with log4j 2.16.

0. Check if your system is vulnerable with the following script, which will search your system for vulnerable libraries.

This script is designed to be run as root, or via sudo:

#!/bin/bash

if [ "$EUID" -ne 0  ]
then echo "Please run $0 as root"
     exit
fi

while read -r log4j_jar ; do
    if [[ -z "$log4j_jar" ]] ; then
        continue
    fi
    if [[ "$log4j_jar" == *"-2.16"* ]] ; then
        echo "Up to date: $log4j_jar"
        continue
    fi
    if [[ "$log4j_jar" == *"-1."* ]] ; then
        echo "1.x - safe: $log4j_jar"
        continue
    fi
    if unzip -l "$log4j_jar" | grep -q JndiLookup.class ; then
        echo "Vulnerable: $log4j_jar"
    else
        echo "Outdated:   $log4j_jar"
    fi
done <<< "$(find / -name 'log4j*.jar')"

1. Retrieve log4j 2.16:

cd /tmp/
curl -O https://dlcdn.apache.org/logging/log4j/2.16.0/apache-log4j-2.16.0-bin.zip 
unzip apache-log4j-2.16.0-bin.zip 

2. Replace other log4j instances on your system with 2.16

The following script will replace vulnerable log4j libraries with 2.16. It searches your system for the vulnerable libraries, and replaces any that are found.

This script is designed to be run as root or via sudo.

#!/bin/bash

set -e

if [ "$EUID" -ne 0 ]
  then echo "Please run $0 as root"
  exit
fi

strip_version() {
    target="$1"
    echo "$target" | sed -E 's|-[0-9.]+.jar|-|'
}

note_not_replaced() {
    target="$1"
    if unzip -l "$log4j_jar" | grep -q JndiLookup.class ; then
        echo >&2 "unable to replace vulnerable $log4j_jar"
        exit_="1"
    else
        echo >&2 "unable to replace $log4j_jar (note: vuln not detected)"
    fi
}

if [[ ! -d /tmp/apache-log4j-2.16.0-bin/ ]] ; then
    echo >&2 "Please retrieve apache log4j 2.16 and unzip it in /tmp before running this script"
    exit 1
fi

while read -r log4j_jar ; do
    if [[ -z "$log4j_jar" ]] ; then
        continue
    fi
    if [[ "$log4j_jar" == *"-2.16"* ]] ; then
        echo "Up to date: $log4j_jar"
        continue
    fi
    if [[ "$log4j_jar" =~ .*-1([0-9.]+).jar ]] ; then
        echo "1.x - safe: $log4j_jar"
        continue
    fi
    if [[ "$log4j_jar" =~ .*\/log4j[^0-9]*(slf4j)?[^0-9]*.jar  ]] ; then
        if unzip -l "$log4j_jar" | grep -q JndiLookup.class ; then
            echo >&2 Cannot replace vulnerable versionless "$log4j_jar"
            export exit_=1
            continue
        fi
        echo "ignoring versionless:  $log4j_jar"
        continue
    fi
    if [[ "$log4j_jar" =~ .*\/log4j[^-]*[0-9.]+.jar  ]] ; then
        if unzip -l "$log4j_jar" | grep -q JndiLookup.class ; then
            echo >&2 Cannot replace vulnerable strange-versioned "$log4j_jar"
            export exit_=1
            continue
        fi
        echo "ignoring strange-versioned:  $log4j_jar"
        continue
    fi
    user_group="$(stat -c "%U:%G" "$log4j_jar")"
    without_version="$(strip_version "$log4j_jar")"
    patched_jar="$(basename "$without_version")2.16.0.jar"
    base_dir="$(dirname "$log4j_jar")"
    echo "replace $log4j_jar ($user_group) - with $patched_jar"
    set -x
    cp /tmp/apache-log4j-2.16.0-bin/"$patched_jar" "$base_dir" || {
        set +x
        note_not_replaced "$log4j_jar"
        continue
    }
    chown "$user_group" "$base_dir/$patched_jar"
    mv "$log4j_jar" "$log4j_jar.orig.vulnerable"
    set +x
done <<< "$(find / -name 'log4j*.jar')"

if [[ "${exit_}" == "1" ]] ; then
    echo "Failed!"
    exit 1
fi

3. You may wish to run the check script from #0 a second time to validate the fix.

4. Please reboot your system after replacing your libraries. This will ensure that the patch becomes fully effective.

FATAL: Could not initialize class com.lingoport.common.velocity.LingoportVelocityWriter

In versions prior to Ireland, if the console output of a Localyzer project shows the following type of error:

 FATAL: Could not initialize class com.lingoport.common.velocity.LingoportVelocityWriter
 java.lang.NoClassDefFoundError: Could not initialize class com.lingoport.common.velocity.LingoportVelocityWriter
    at com.lingoport.plugins.jenkinsgyzrlrmplugin.BuildLRM.saveProjectSettings(BuildLRM.java:860)

or if the error is like:

 FATAL: org/apache/log4j/Logger
 java.lang.ClassNotFoundException: org.apache.log4j.Logger
    at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1393)
    at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1348)
    at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1094)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
 Caused: java.lang.NoClassDefFoundError: org/apache/log4j/Logger
    at com.lingoport.common.velocity.LingoportVelocityWriter.<clinit>(LingoportVelocityWriter.java:45)

it is likely that a Log4j is actually missing from the classpath. In that case,

  copy the  lingoport/LRM-server-xx/lib/log4j-x.y.z.jar to /var/lib/jenkins/plugins/jenkins-gyzr-lrm-plugin/WEB-INF/lib/.

This should only happen with versions prior to Ireland.