How to Fix CVE-2017-9791: Improper input validation in Apache Struts

WARNING: This vulnerability is on the CISA Known Exploited Vulnerabilities catalog (added 2022-02-10). Federal civilian agencies must remediate by 2022-08-10. Treat it as active exploitation, not theoretical.

What is CVE-2017-9791?

The Struts 1 plugin in Apache Struts 2.1.x and 2.3.x might allow remote code execution via a malicious field value passed in a raw message to the ActionMessage.

Am I affected?

Run the version check that matches your platform:

# Linux
dpkg -s libstruts2-core-java 2>/dev/null | grep -i version
rpm -q libstruts2-core-java 2>/dev/null
libstruts2-core-java --version 2>/dev/null

Compare what you see against the Affected row above (Apache Software Foundation Apache Struts 2.1.x series, 2.3.x series). If your build sits inside that range, you are exposed and should patch.

How to fix CVE-2017-9791

The primary fix is to upgrade Apache Struts to the patched build. Use the commands for your platform below; the patched version listed in the vendor advisory is: See vendor advisory.

Ubuntu / Debian

sudo apt-get update
sudo apt-get install --only-upgrade libstruts2-core-java
libstruts2-core-java --version 2>/dev/null || dpkg -s libstruts2-core-java | grep -i version

RHEL / CentOS / Rocky / AlmaLinux

sudo dnf upgrade --security libstruts2-core-java -y
rpm -q libstruts2-core-java

SUSE / openSUSE

sudo zypper patch --category security
rpm -q libstruts2-core-java

Complete PowerShell remediation script (Windows)

# Fix script for CVE-2017-9791 affecting Apache Struts
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2017-9791-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append

try {
    Write-Host "[1/4] Detecting installed version of Apache Struts"
    $pkg = winget list --id "Apache_Struts" 2>$null
    Write-Host $pkg

    Write-Host "[2/4] Backing up configuration"
    $backup = "C:\Backup\Apache_Struts-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\Apache_Struts" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Applying upgrade to latest"
    winget upgrade --id "Apache_Struts" --silent --accept-source-agreements --accept-package-agreements
    # Fallback: Windows Update for OS-level fixes
    if ($LASTEXITCODE -ne 0) {
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verifying patched build"
    winget list --id "Apache_Struts"
    Write-Host "Fix applied. Reboot if prompted."
    exit 0
} catch {
    Write-Error "Patch failed: $_"
    exit 1
} finally {
    Stop-Transcript
}

Complete Bash remediation script (Linux)

#!/usr/bin/env bash
# Fix script for CVE-2017-9791 affecting Apache Struts
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2017-9791-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detecting installed version"
if command -v dpkg >/dev/null; then
    dpkg -s libstruts2-core-java 2>/dev/null | grep -i version || echo "libstruts2-core-java not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q libstruts2-core-java || echo "libstruts2-core-java not installed via rpm"
fi

echo "[2/4] Backing up configuration"
BACKUP="/root/backup-cve-2017-9791-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/libstruts2-core-java /etc/libstruts2-core-java.d /etc/libstruts2-core-java.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Applying upgrade (target: latest)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y libstruts2-core-java
elif command -v dnf >/dev/null; then
    dnf upgrade --security -y libstruts2-core-java
elif command -v yum >/dev/null; then
    yum update -y libstruts2-core-java
elif command -v zypper >/dev/null; then
    zypper --non-interactive patch --category security
fi

echo "[4/4] Verifying patched build"
if command -v dpkg >/dev/null; then
    dpkg -s libstruts2-core-java 2>/dev/null | grep -i version
elif command -v rpm >/dev/null; then
    rpm -q libstruts2-core-java
fi
echo "Done. Restart any running daemons that loaded the old library."

If you can't patch immediately

If you cannot apply the patched version today, restrict exposure with one of the following runnable controls. None replace the patch.

Network restriction (Linux, nftables)

# Block inbound traffic to the affected service from untrusted networks
sudo nft add table inet filter
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }'
sudo nft 'add rule inet filter input tcp dport {443, 80} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Service-level fallback

# If the affected feature is optional, stop the service until the patch is applied
sudo systemctl stop libstruts2-core-java
sudo systemctl disable libstruts2-core-java

How to verify the fix worked

# Linux
libstruts2-core-java --version 2>/dev/null || dpkg -s libstruts2-core-java | grep -i version
rpm -q libstruts2-core-java 2>/dev/null || true

# Windows
winget list | findstr /I "libstruts2-core-java"
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above the patched build documented in the advisory. Restart any services that loaded the old library (systemctl restart <service> on Linux, restart the Windows service or reboot when prompted). For network appliances, run show version on the device and confirm the build matches the patched release.

Frequently asked questions

Related fixes

Other vulnerabilities in the same area that are worth patching alongside this one:

• How to Fix CVE-2017-5638: Remote code execution in Apache Struts — Remote code execution in Apache Struts
• How to Fix CVE-2017-12617: Unrestricted File Upload in Apache Tomcat — Unrestricted File Upload in Apache Tomcat
• How to Fix CVE-2017-9805: Deserialization of untrusted data in Apache Struts , Deserialization of untrusted data in Apache Struts
• How to Fix CVE-2017-12615: Unrestricted File Upload in Apache Tomcat , Unrestricted File Upload in Apache Tomcat

Is CVE-2017-9791 actually being exploited?

According to the data sources above, yes, CISA has it listed as actively exploited. Either way, the fix is the same: apply the vendor patch.

Do I need to reboot after patching?

For OS or kernel updates, yes. For most userland packages a systemctl restart <service> is enough. Any process that loaded the old shared library keeps using it until restarted, so when in doubt, reboot.

What is the CVSS score?

9.8 (critical). Refer to the vendor advisory for the exact vector string.

Where is the official advisory?

See the References section at the bottom of this page; the vendor's URL is the authoritative source for affected builds and patched versions.

References

• Official vendor advisory: http://www.oracle.com/technetwork/security-advisory/alert-cve-2017-9805-3889403.html
• NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-9791
• CISA KEV catalog entry: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• http://www.securityfocus.com/bid/99484
• https://www.exploit-db.com/exploits/42324/
• http://struts.apache.org/docs/s2-048.html
• http://www.securitytracker.com/id/1038838

*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*