Patch

CVE-2024-9143

with vRx

Vulnerability Overview

CVE Name

CVE-2024-9143

Severity

4.3

Low

CVE Description

Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the field polynomial can lead to out-of-bounds memory reads or writes. Impact summary: Out of bound memory writes can lead to an application crash or even a ...

Show less

Latest Patch info

There is no patch available at the moment, but you can use our script.

Patch Name

Date

Script

Script Type

Remediation script

Copy script

Introduction The discovery of CVE-2024-9143, a critical vulnerability in OpenSSL versions prior to 3.4.0, has raised significant security concerns across platforms. Exploiting this vulnerability could lead to denial-of-service attacks or other undefined behavior due to improper handling of crafted elliptic curve parameters. In this post, we present a cross-platform remedy script that automates the process of detecting, upgrading, and verifying OpenSSL installations on Linux, macOS, Windows (via WSL or Git Bash), and even within Docker containers. Understanding the Challenge OpenSSL powers secure communication protocols across millions of systems. With older or vulnerable versions like 3.3.2, your system may be exposed to potential exploits. While most package managers update OpenSSL automatically, not all systems provide the latest secure versions immediately. Our remedy script bridges this gap by manually upgrading OpenSSL to 3.4.0, the secure release. Features of the Remedy Script Cross-Platform Compatibility: Automatically detects the operating system and applies the appropriate update or manual installation process. Docker Integration: Checks and updates OpenSSL within running Docker containers. Automatic Testing: Verifies the new OpenSSL version and tests it against crafted inputs to ensure the vulnerability is mitigated. Logging and Cleanup: Keeps the environment clean by removing temporary files after execution. How to Use the Script Save the script as remedy.sh. Make it executable: chmod +x remedy.sh Run the script: sudo ./remedy.sh Benefits of the Script Cross-Platform: Handles Linux, macOS, Windows (via WSL), and Docker environments seamlessly. Automated Testing: Verifies the upgrade and ensures vulnerability mitigation. Future-Proof: Upgrades to the latest secure version (currently 3.4.0) from the official GitHub repository. Conclusion By automating the upgrade process with this remedy script, you can efficiently secure your systems and containers from CVE-2024-9143. Whether you're managing a single system or a fleet of Docker containers, this script provides a reliable solution for mitigating OpenSSL vulnerabilities. Stay secure, and keep your dependencies up to date!

Read less

#!/bin/bash

set -e

echo "Starting cross-platform remedy for CVE-2024-9143..."

SECURE_VERSION="3.4.0"
TEST_FILE="ec_remedy_test.pem"
INSTALL_DIR="/usr/local"
OPENSSL_URL="https://github.com/openssl/openssl/releases/download/openssl-$SECURE_VERSION/openssl-$SECURE_VERSION.tar.gz"
OS_TYPE=$(uname -s)

check_openssl_version() {
    if ! command -v openssl &> /dev/null; then
        echo "OpenSSL is not installed. Please install it and try again."
        exit 1
    fi

OPENSSL_VERSION=$(openssl version | awk '{print $2}')
    echo "Detected OpenSSL version: $OPENSSL_VERSION"

if [[ "$OPENSSL_VERSION" > "$SECURE_VERSION" ]]; then
        echo "Your OpenSSL version ($OPENSSL_VERSION) is secure. No action needed."
        exit 0
    fi

echo "OpenSSL version is vulnerable. Proceeding with the remedy..."
}

update_openssl() {
    echo "Attempting to update OpenSSL using the system package manager..."

case "$OS_TYPE" in
        Linux)
            if [ -f /etc/debian_version ]; then
                echo "Detected Debian/Ubuntu system. Updating OpenSSL..."
                sudo apt update
                sudo apt install --only-upgrade openssl -y
            elif [ -f /etc/redhat-release ]; then
                echo "Detected RHEL/CentOS system. Updating OpenSSL..."
                sudo yum update openssl -y
            else
                echo "Unsupported Linux distribution. Proceeding with manual upgrade..."
                manual_upgrade
            fi
            ;;
        Darwin)
            echo "Detected macOS. Updating OpenSSL via Homebrew..."
            if ! command -v brew &> /dev/null; then
                echo "Homebrew is not installed. Installing Homebrew..."
                /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
            fi
            brew update
            brew upgrade openssl
            ;;
        *)
            echo "Unsupported OS: $OS_TYPE. Proceeding with manual upgrade..."
            manual_upgrade
            ;;
    esac
}

manual_upgrade() {
    echo "Manually upgrading OpenSSL to version $SECURE_VERSION..."

if command -v wget &> /dev/null; then
        wget $OPENSSL_URL || wget --no-check-certificate $OPENSSL_URL
    elif command -v curl &> /dev/null; then
        curl -O $OPENSSL_URL || curl -k -O $OPENSSL_URL
    else
        echo "Neither wget nor curl is available. Please install one to proceed."
        exit 1
    fi

tar -xvzf "openssl-$SECURE_VERSION.tar.gz"
    cd "openssl-$SECURE_VERSION"

echo "Configuring and building OpenSSL..."
    ./config --prefix=$INSTALL_DIR --openssldir=$INSTALL_DIR/ssl
    make
    sudo make install

echo "Updating symbolic links..."
    sudo ln -sf /usr/local/bin/openssl /usr/bin/openssl
    cd ..
    rm -rf "openssl-$SECURE_VERSION" "openssl-$SECURE_VERSION.tar.gz"

echo "Manual upgrade completed."
}

update_docker_containers() {
    if command -v docker &> /dev/null; then
        echo "Docker is installed. Checking for vulnerable OpenSSL versions in containers..."
        docker ps --format ": " | while read container; do
            container_id=$(echo $container | awk -F: '{print $1}')
            image_name=$(echo $container | awk -F: '{print $2}')

echo "Checking container $container_id ($image_name)..."
            docker exec $container_id bash -c "openssl version" || continue

echo "Updating OpenSSL in container $container_id ($image_name)..."
            docker exec $container_id bash -c "
                wget $OPENSSL_URL -O /tmp/openssl.tar.gz || curl -k -O $OPENSSL_URL -o /tmp/openssl.tar.gz
                tar -xvzf /tmp/openssl.tar.gz -C /tmp
                cd /tmp/openssl-$SECURE_VERSION
                ./config && make && make install
                rm -rf /tmp/openssl.tar.gz /tmp/openssl-$SECURE_VERSION"
            echo "OpenSSL updated in container $container_id ($image_name)."
        done
    else
        echo "Docker is not installed. Skipping Docker checks."
    fi
}

verify_remedy() {
    NEW_VERSION=$(openssl version | awk '{print $2}')
    if [[ "$NEW_VERSION" > "$SECURE_VERSION" ]]; then
        echo "OpenSSL successfully upgraded to a secure version ($NEW_VERSION)."
    else
        echo "Failed to upgrade OpenSSL. Current version: $NEW_VERSION. Please investigate further."
        exit 1
    fi
}

create_test_file() {
    cat <<EOF > $TEST_FILE
-----BEGIN EC PARAMETERS-----
BgUrgQQACg==
-----END EC PARAMETERS-----
EOF
    echo "Crafted elliptic curve parameter test file created: $TEST_FILE"
}

test_remedy() {
    echo "Testing OpenSSL with crafted elliptic curve parameters to verify the remedy..."
    OUTPUT=$(openssl ecparam -in $TEST_FILE -text -noout 2>&1)
    if [ $? -eq 0 ]; then
        echo "OpenSSL successfully handled the crafted input. Vulnerability mitigated."
        echo "Output:"
        echo "$OUTPUT"
    else
        echo "OpenSSL failed to handle the crafted input. Please verify the upgrade process."
        echo "Error Output:"
        echo "$OUTPUT"
    fi
}

check_openssl_version
update_openssl
manual_upgrade
verify_remedy
create_test_file
test_remedy
update_docker_containers

rm -f $TEST_FILE
echo "Remedy script completed successfully. Test file removed."

Copy script

Affected OS & Apps

No items found.

4.8

Patch faster and smarter
with vRx

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

More than 600 customers trust vRx:

Solution

‍Remediate faster with vRx

Patch Management

vRx automatically deploys patches across all systems, cutting patching time by 80%.

Scripting Engine

vRx’s scripting engine solves complex vulnerabilities, like log4j, with built-in or custom scripts.

Patchless Protection

vRx’s Patchless Protection secures vulnerable apps and reduces risk while maintaining functionality.

Book a demo

4.9

4.8

4.9

Hear from our Customers

Valuable resources saved

"Before vRx, we would spend countless hours manually finding and verifying patches. We saved so much time (and headache!)."

Anonymous IT Operations Lead

IT Operations Lead

Third-party software patching is the most valuable feature.

"We have automated third-party patching on specific software, improving efficiency by 80%. vRx has reduced our patching time, which has improved our operations. It is more robust than other solutions because it offers better third-party remediation."

Billy Turner

VP, Managed Technology & Services

Single source of truth, capable of handling any application in our fleet

"vRx gives a single pane of glass to see what patches needed to go out and what sort of vulnerabilities we have on our Windows machines. Our meantime to remediate vulnerabilities has gone down by about 60% to 70%."

Peter Fallowfield

IT Manager

60% faster remediation, many hours saved

"Typically, with our previous solution of ManageEngine, it took about three hours to patch Windows Server, and now, that is less than an hour. It means less downtime for the business each month when we do patches."

Anonymous Security Analyst

Security Analyst

Great patching capabilities, helpful dashboard, and excellent support

"vRx has saved us an incredible amount of time. We can just rely on the automated system and the schedules we've set. It's a huge time saver. It's saved us hundreds of hours."

Michael Cortez

Sr. Director of IT

My favorite feature is Patchless Protection

"With Vicarius' vRx, I've never seen a patch that failed or had to be rolled back. We're saving quite a bit of time. Our clients using vRx haven't had any issues, and they've easily established patching for all their endpoints. "

Jeremy Herman

Security Engineer

Unified vulnerability discovery, prioritization, and remediation

"Vicarius streamlines vulnerability management between IT & Security by directly linking identified vulnerabilities to required patches, enhancing efficiency. The automation process has saved at least 30 percent of our manual tasks."

Wayne Ajimine

Information Security Professional

Patchless Protection is an incredible technology!

"vRx reduces the time customers spend on patching by reducing the overhead on the administrators, allowing them to do additional work. It saves time they would spend addressing the patching process, follow-ups, etc."

Antwune Gray

VP IT Security and Services