Threats / Samba / CVE-2017-7494
CVE-2017-7494
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Samba vulnerability
Samba remote code execution via malicious shared library upload and execution on writable shares, exploited in ransomware campaigns.
Verdict
Today item, not a backlog item.
A remote attacker can upload a crafted shared library to a writable Samba share and trigger server-side execution, achieving unauthenticated code execution. Active exploitation in ransomware operations confirms critical risk.
CISA KEV Yes · 2023-03-303Ransomware use Flagged3EPSS 0.99448 (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
9 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-03-30), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.99448 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Samba, Samba. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-94 Code Injection — 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 identify a writable share on the target Samba server.
Business
Exposed writable shares indicate insufficient access controls and network segmentation.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I upload a malicious shared library file to the writable share.
Business
Lack of file type validation on shares enables arbitrary code staging.
3
Lateral reach — past segmentation narrative 3
Attacker
I trigger the Samba server to load and execute the uploaded library.
Business
Unsafe library loading mechanisms allow attacker code to run with server privileges.
4
Data at risk — exfiltration narrative 4
Attacker
I achieve remote code execution with Samba process privileges.
Business
Compromised file servers become pivot points for lateral movement and data exfiltration.
5
Lights out — disruption & extortion narrative 5
Attacker
I deploy ransomware or establish persistent access across the network.
Business
Active ransomware campaigns targeting this vulnerability result in operational shutdown and financial extortion.
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