Threats / Fortra / CVE-2023-0669
CVE-2023-0669
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Fortra GoAnywhere MFT vulnerability
Fortra GoAnywhere MFT contains a pre-authentication remote code execution vulnerability in the License Response Servlet caused by unsafe deserialization of attacker-controlled objects.
Verdict
Today item, not a backlog item.
An unauthenticated attacker can exploit unsafe object deserialization in the License Response Servlet to execute arbitrary code on affected GoAnywhere MFT instances before authentication, enabling full system compromise and data exfiltration.
CISA KEV Yes · 2023-02-103Ransomware use Flagged3EPSS 0.99999 (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
733 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 2023-02-10), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.99999 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Fortra, GoAnywhere MFT. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-502 Deserialization of Untrusted Data — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
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
I craft a malicious serialized Java object and send it to the License Response Servlet endpoint without authentication.
Business
The organization's file transfer infrastructure is directly exposed to remote code execution from the internet.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I trigger deserialization of my payload, which executes arbitrary code with the privileges of the GoAnywhere MFT process.
Business
Attackers gain immediate command execution capability on critical data transfer systems.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish persistence and move laterally through the network to access sensitive files and credentials stored in the MFT system.
Business
Confidential business data, customer information, and intellectual property are compromised and exfiltrated.
4
Data at risk — exfiltration narrative 4
Attacker
I deploy ransomware or wiper malware across connected systems to encrypt or destroy data.
Business
Operations halt, recovery costs escalate, and regulatory fines accumulate from data breach notifications.
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