dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 30 Aug 2022. Known ransomware use
Debian LinuxOperating system · Debian

CVE-2022-30333

HIGH · 7.5 CVSS v3.1 Published 2022-05-09
Fix available
A fix is available. Upgrade to 6.12 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
RARLAB UnRAR before 6.12 on Linux and UNIX allows directory traversal to write to files during an extract (aka unpack) operation, as demonstrated by creating a ~/.ssh/authorized_keys file. NOTE: WinRAR and Android RAR are unaffected.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

UnRAR before version 6.12 on Linux and UNIX contains a path traversal vulnerability allowing attackers to write files outside the intended extraction directory during unpack operations. Attackers can craft malicious RAR archives with specially crafted file paths (e.g., ../../.ssh/authorized_keys) to overwrite system files and potentially gain remote code execution.

MitigationUpgrade UnRAR to version 6.12 or later. If immediate patching is not feasible, isolate extraction processes in sandboxed environments and ensure extracted files are placed in secure, non-privileged directories with restricted permissions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Debian LinuxOperating system
Affected:= 10.0
UnrarApplication
Affected:< 6.12

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify UnRAR is installed
    Run 'which unrar' or 'dpkg -l | grep unrar' (Debian/Ubuntu) to determine if the unrar utility is present on the system
    Affected if UnRAR is installed and the version is below 6.12
  2. Determine installed UnRAR version
    Run 'unrar version' or 'unrar -?' to display the version number. Compare the displayed version against the affected range (less than 6.12)
    Affected if The version number returned is less than 6.12 or shows the vulnerable release
  3. Identify processes or users that extract RAR archives
    Review cron jobs, scripts, and user activities that invoke 'unrar x', 'unrar e', or 'unrar' commands, particularly on archives from untrusted sources
    Affected if Automated or user-driven RAR extraction occurs on potentially untrusted archives
  4. Audit recent extraction directories for path traversal artifacts
    Search extraction logs or directories for unusual path patterns such as '../' sequences, or check for unexpected files appearing outside the intended target directory after RAR operations
    Affected if Evidence exists of files created outside the intended extraction directory using '../' sequences

The system is affected if UnRAR with a version lower than 6.12 is installed and processes RAR archives, especially from untrusted sources, allowing attackers to write files outside the extraction directory.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.12 or later
Fixed in 6.12
Vendor patch www.rarlab.com →
Interim mitigation

Upgrade UnRAR to version 6.12 or later. If immediate patching is not feasible, isolate extraction processes in sandboxed environments and ensure extracted files are placed in secure, non-privileged directories with restricted permissions.

Recommended fix High confidence

UnRAR 6.12 or later

  1. 1. Check the current installed version of UnRAR by running: unrar -version
  2. 2. If the version is below 6.12, download UnRAR 6.12 or later from the official vendor website: www.rarlab.com
  3. 3. Extract the downloaded archive and navigate to the UnRAR makefile directory
  4. 4. Build and install the updated UnRAR binary following the vendor's installation instructions
  5. 5. Verify the installation was successful by running: unrar -version
  6. 6. Ensure the displayed version is 6.12 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Debian Linux Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-30333 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-30333 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data