Threats / RARLAB / CVE-2022-30333
CVE-2022-30333
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
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-094Ransomware use Flagged4EPSS 0.99085 (verify live)5Exploit Weaponized · public PoC6CVSS 7.5 (CISA)3CISA SSVC Exploitation: active · Automatable: yes · Impact: total3
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
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.
Probability (EPSS)
EPSS 0.99085 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N) · Affected: RARLAB, UnRAR. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-22 Path Traversal, CWE-59 Link Following — weakness family: Path traversal / file.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 92 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
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 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’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by mitreCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.