How to Fix CVE-2017-10271: Missing authentication in WebLogic Server
| Severity | 7.5 (High) |
|---|---|
| Actively exploited? | Yes, listed in CISA KEV (added 2022-02-10) |
| Affected | Oracle Corporation WebLogic Server 10.3.6.0.0, 12.1.3.0.0, 12.2.1.1.0, 12.2.1.2.0 |
| Fixed in | See vendor advisory |
| Type (CWE) | CWE-306: Missing Authentication for Critical Function |
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-10271?
Vulnerability in the Oracle WebLogic Server component of Oracle Fusion Middleware (subcomponent: WLS Security). Supported versions that are affected are 10.3.6.0.0, 12.1.3.0.0, 12.2.1.1.0 and 12.2.1.2.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via T3 to compromise Oracle WebLogic Server. Successful attacks of this vulnerability can result in takeover of Oracle WebLogic Server.
Am I affected?
Run the version check that matches your platform:
# Linux
dpkg -s weblogic 2>/dev/null | grep -i version
rpm -q weblogic 2>/dev/null
weblogic --version 2>/dev/null
Compare what you see against the Affected row above (Oracle Corporation WebLogic Server 10.3.6.0.0, 12.1.3.0.0, 12.2.1.1.0, 12.2.1.2.0). If your build sits inside that range, you are exposed and should patch.
How to fix CVE-2017-10271
The primary fix is to upgrade WebLogic Server 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 weblogic
weblogic --version 2>/dev/null || dpkg -s weblogic | grep -i version
RHEL / CentOS / Rocky / AlmaLinux
sudo dnf upgrade --security weblogic -y
rpm -q weblogic
SUSE / openSUSE
sudo zypper patch --category security
rpm -q weblogic
Complete PowerShell remediation script (Windows)
# Fix script for CVE-2017-10271 affecting WebLogic Server
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.
$ErrorActionPreference = "Stop"
$LogPath = "C:\Logs\CVE-2017-10271-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 WebLogic Server"
$pkg = winget list --id "WebLogic_Server" 2>$null
Write-Host $pkg
Write-Host "[2/4] Backing up configuration"
$backup = "C:\Backup\WebLogic_Server-$(Get-Date -Format yyyyMMdd)"
New-Item -ItemType Directory -Force $backup | Out-Null
Get-ChildItem "C:\ProgramData\WebLogic_Server" -ErrorAction SilentlyContinue |
Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue
Write-Host "[3/4] Applying upgrade to latest"
winget upgrade --id "WebLogic_Server" --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 "WebLogic_Server"
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-10271 affecting WebLogic Server
# Detect -> backup -> upgrade -> verify -> log.
set -euo pipefail
LOG="/var/log/cve-2017-10271-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 weblogic 2>/dev/null | grep -i version || echo "weblogic not installed via dpkg"
elif command -v rpm >/dev/null; then
rpm -q weblogic || echo "weblogic not installed via rpm"
fi
echo "[2/4] Backing up configuration"
BACKUP="/root/backup-cve-2017-10271-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/weblogic /etc/weblogic.d /etc/weblogic.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 weblogic
elif command -v dnf >/dev/null; then
dnf upgrade --security -y weblogic
elif command -v yum >/dev/null; then
yum update -y weblogic
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 weblogic 2>/dev/null | grep -i version
elif command -v rpm >/dev/null; then
rpm -q weblogic
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 weblogic
sudo systemctl disable weblogic
How to verify the fix worked
# Linux
weblogic --version 2>/dev/null || dpkg -s weblogic | grep -i version
rpm -q weblogic 2>/dev/null || true
# Windows
winget list | findstr /I "weblogic"
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-2026-35244: Access control in Oracle Hyperion Infrastructure Technology — Access control in Oracle Hyperion Infrastructure Technology
- How to Fix CVE-2026-21986: Critical Vulnerability in Oracle VM VirtualBox — Critical Vulnerability in Oracle VM VirtualBox
- How to Fix CVE-2026-21973: Critical Vulnerability in Oracle FLEXCUBE Investor Servicing , Critical Vulnerability in Oracle FLEXCUBE Investor Servicing
- How to Fix CVE-2026-34281: Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Oracle Solaris executes to compromise Oracle Solaris. While the vulnerability is in Oracle Solaris, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle Solaris , Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Oracle Solaris executes to compromise Oracle Solaris. While the vulnerability is in Oracle Solaris, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle Solaris
- How to Fix CVE-2026-21939: Critical Vulnerability in Oracle Database Server , Critical Vulnerability in Oracle Database Server
Is CVE-2017-10271 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?
7.5 (high). 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: https://github.com/c0mmand3rOpSec/CVE-2017-10271
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-10271
- CISA KEV catalog entry: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- https://www.exploit-db.com/exploits/43458/
- http://www.securitytracker.com/id/1039608
- http://www.securityfocus.com/bid/101304
- http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html
*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.*