Patch

CVE-2023-50164

with vRx

Vulnerability Overview

CVE Name

CVE-2023-50164

Severity

9.8

Critical

CVE Description

An attacker can manipulate file upload params to enable paths traversal and under some circumstances this can lead to uploading a malicious file which can be used to perform Remote Code Execution. Users are recommended to upgrade to versions Struts 2.5.33 ...

Show less

Latest Patch info

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

Patch Name

security@apache.org

Date

07.12.2023

Script

Script Type

Remediation script

Copy script

This script is a Python program that automates the process of updating the version of the Apache Struts library in a Maven project. The script performs the following tasks: Fetch Remote Tags: Uses the git ls-remote command to retrieve a list of tags from a specified remote Git repository (in this case, the Apache Struts repository on GitHub). Extract Version Numbers: Parses the retrieved tags to extract version numbers. It modifies the tag names to get a standard version format. Get All Versions: Obtains a list of all possible versions of the Apache Struts library from the remote Git repository. Get Current Version: Executes the Maven command mvn versions:display-dependency-updates to determine the current version of the Apache Struts library in the project. It specifically looks for updates related to the org.apache.struts:struts2-core dependency. Find Next Good Version: Defines ranges of vulnerable versions of Apache Struts. Compares the current version with the list of all versions and identifies the next non-vulnerable version that is higher than the current version. Update Version: Uses Maven commands (mvn versions:set and mvn versions:update-properties) to update the version of the Apache Struts library in the project. The main goal of this script is to automate the process of checking for updates in the Apache Struts core library, finding the next non-vulnerable version, and updating the library version in a Maven project. It is particularly focused on avoiding versions within certain vulnerable ranges.

Read less

import sys
import subprocess
from packaging import version

def fetch_remote_tags(remote_url):
    # Run the git ls-remote command to get the list of tags
    command = f'git ls-remote --tags {remote_url}'
    result = subprocess.run(command, shell=True, stdout=subprocess.PIPE, text=True)
    output = result.stdout

# Extract tag names from the output, excluding unwanted tags
    tag_lines = [line.split()[-1].split('/')[-1] for line in output.split('\n') if line.strip()]
    tags = [tag for tag in tag_lines if '^{}' not in tag and 'RC' not in tag]

return tags

def extract_version_number(tag):
    # Extract version numbers from the tag
    version_number = tag.replace('STRUTS_', '').replace('_BETA', '-BETA').replace('_', '.')
    return version_number

def get_all_versions():
    # Get all possible versions from the remote git repo
    remote_url = 'https://github.com/apache/struts'
    tags = fetch_remote_tags(remote_url)
    version_list = [extract_version_number(tag) for tag in tags]
    return version_list

def get_current_version():
    # Run the mvn versions:display-dependency-updates command to get the current version
    command = 'mvn versions:display-dependency-updates -Dincludes=org.apache.struts:struts2-core'
    result = subprocess.run(command, shell=True, stdout=subprocess.PIPE, text=True)
    output_lines = result.stdout.split('\n')

if 'No dependencies in Dependencies have newer versions.' in result.stdout:
        print('[-] No dependencies have newer versions.')
        sys.exit()

for line in output_lines:
        if 'org.apache.struts:struts2-core' in line:
            return line.split()[3]

return None

def find_next_good_version(current_version):
    # Define vulnerable version ranges
    vulnerable_ranges = [("2.0.0", "2.3.37"), ("2.5-BETA1", "2.5.32"), ("6.0.0", "6.3.0.1")]
    # Get all possible versions from remote git repo
    all_struts_versions = get_all_versions()

current_version_obj = version.parse(current_version)
    for version_str in all_struts_versions:
        version_obj = version.parse(version_str)

# Check if the version is non-vulnerable
        is_vulnerable = any(version.parse(start) <= version_obj <= version.parse(end) for start, end in vulnerable_ranges)

if not is_vulnerable and version_obj > current_version_obj:
            return str(version_obj)

def update_version(new_version):
    # Update the version using mvn commands
    set_version_command = f'mvn versions:set -DnewVersion={new_version} -DallowSnapshots=true -Dincludes=org.apache.struts:struts2-core'
    update_properties_command = 'mvn versions:update-properties -Dincludes=org.apache.struts:*'

subprocess.run(set_version_command, shell=True)
    subprocess.run(update_properties_command, shell=True)

def main():
    # Step 1: Get the current version
    current_version = get_current_version()

if current_version is None:
        print("[-] Failed to retrieve current version.")
        sys.exit()

print(f"[+] Current version of org.apache.struts:struts2-core: {current_version}")

# Step 2: Find the next non-vulnerable version
    next_good_version = find_next_good_version(current_version)

if next_good_version is None:
        print("[-] No next non-vulnerable version found.")
        sys.exit()

print(f"[+] Next non-vulnerable version: {next_good_version}")

# Step 3: Update the version
    update_version(next_good_version)

print(f"[+] Version updated to {next_good_version}")

if __name__ == "__main__":
    main()

Copy script

Affected OS & Apps

Struts

Apache

4.8

Patch faster and smarter
with vRx

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Trusted by 600+ customers:

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