Threats / Oracle / CVE-2017-10271
CVE-2017-10271
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Oracle WebLogic Server vulnerability
Oracle WebLogic Server remote code execution vulnerability enabling unauthenticated attackers to execute arbitrary code on affected systems.
Verdict
Today item, not a backlog item.
Critical vulnerability with high exploitation prevalence. Active exploitation in the wild combined with ransomware campaigns demonstrates immediate threat. Organizations running vulnerable WebLogic instances face direct compromise risk.
CISA KEV Yes · 2022-02-103Ransomware use Flagged3EPSS 0.99934 (verify live)4Exploit Weaponized · public PoC5
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
808 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-02-10), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.99934 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Oracle, WebLogic Server. Confirm exact fixed builds in the vendor advisory.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
Identify and probe for exposed WebLogic Server instances on the network perimeter.
Business
Exposed infrastructure becomes reconnaissance target for threat actors scanning for vulnerable deployments.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
Craft and deliver exploit payload to trigger remote code execution without authentication.
Business
Initial access achieved; attacker gains code execution context within enterprise systems.
3
Lateral reach — past segmentation narrative 3
Attacker
Execute commands to establish persistence and deploy secondary payloads or ransomware.
Business
Systems encrypted or data exfiltrated; operational disruption and potential financial extortion.
4
Data at risk — exfiltration narrative 4
Attacker
Pivot laterally to connected systems and escalate privileges within the environment.
Business
Compromise spreads beyond initial target; scope of incident expands across infrastructure.
5
Lights out — disruption & extortion narrative 5
Attacker
Maintain access for data theft, sabotage, or continued extortion activities.
Business
Prolonged breach increases regulatory exposure, reputational damage, and recovery costs.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05