basicsecurity.net
Proof, not just disclosure.
Threats / RARLAB / CVE-2022-30333
CVE-2022-30333 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

RARLAB UnRAR vulnerability

RARLAB UnRAR on Linux and UNIX contains a directory traversal vulnerability allowing attackers to write arbitrary files during extract operations via path manipulation.

Verdict

Today item, not a backlog item.

A directory traversal flaw in UnRAR permits attackers to escape intended extraction directories and overwrite files on affected systems. The vulnerability has been actively exploited in ransomware campaigns and carries high exploitation likelihood.

CISA KEV Yes · 2022-08-093Ransomware use Flagged3EPSS 0.98975 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit 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
6 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-08-09), flagged for known ransomware use.
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.98975 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: RARLAB, UnRAR. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-22 Path Traversal, CWE-59 Link Following — weakness family: Path traversal / file.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious RAR archive with path traversal sequences that bypass directory restrictions during extraction.
Business
Attackers gain ability to place malicious payloads or overwrite critical system files on customer endpoints.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I distribute the weaponized archive through email, downloads, or file-sharing platforms targeting UnRAR users.
Business
Organizations face widespread compromise risk as users unknowingly extract archives containing traversal payloads.
3

Lateral reach — past segmentation narrative 3

Attacker
I execute ransomware deployment by writing encrypted payloads and ransom notes to arbitrary filesystem locations.
Business
Ransomware campaigns leverage this vector to establish persistence and encrypt critical business data at scale.
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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • Ransomware-use flag (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 6 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by mitre (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by mitreCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.