CVE Tools

CVE-2018-20251

CVE-2018-20251 is a path traversal in WinRAR GmbH WinRAR (CVSS 5.5, Medium).

Exploitation likely. EPSS gives it a 31% chance of exploitation in the next 30 days. A vendor fix is available.

Check it yourself

No ready-made check. Neither Nuclei nor OpenVAS has one for this CVE yet.

Request a scan

Published Updated Sources: CVE.org, NVD, BDU

What to do

The vendor has published a fix. Version details are below where the sources state them.

  • Check Point Software Technologies Ltd. WinRARAffected: All versions prior and including 5.61Upgrade to: not statedStated by: CVE record
  • Rarlab WinrarAffected: ≤ 5.61Upgrade to: after 5.61Stated by: NVD
  • WinRAR GmbH WinRARAffected: before 5.70 Beta 1Upgrade to: not statedStated by: BDU

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check whether you run WinRAR and what version is installed (look for the WinRAR version number).
  2. If your WinRAR version is 5.61 or older, plan an upgrade now.
  3. Upgrade WinRAR to the fixed version: 5.70 Beta 1.

What it is

From the CVE record

In WinRAR versions prior to and including 5.61, there is path traversal vulnerability when crafting the filename field of the ACE format. The UNACE module (UNACEV2.dll) creates files and folders as written in the filename field even when WinRAR validator noticed the traversal attempt and requestd to abort the extraction process. the operation is cancelled only after the folders and files were created but prior to them being written, therefore allowing the attacker to create empty files and folders everywhere in the file system.

In plain language

Written by AI from the record

If you use WinRAR (5.61 or older), a specially made ACE archive can cause WinRAR to create empty files and folders in unintended locations while extracting—so you should update to a newer version.

Unauthenticated path traversal in WinRAR’s ACE extraction (UNACEV2.dll) allows crafted “filename” fields to escape intended directories and create filesystem entries before extraction is fully aborted.

If you're affected

  • Unexpected files created
  • Folder clutter and disruption
  • Operational disruption during extraction
  • Potential access to planted placeholders

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS98th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

31% chance of exploitation activity in the next 30 days, which ranks it in the 98th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

22 events over 2787 days, from the signal feeds we watch.

  1. EPSS band change0 → moderateepss band change
  2. EPSS band changemoderate → 0epss band change
  3. EPSS band change0 → moderateepss band change
  4. EPSS band changemoderate → 0epss band change
  5. EPSS band change0 → moderateepss band change
  6. EPSS band changemoderate → 0epss band change

Affected products

Technical detail

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

Scored 5.5 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction RequiredA user must click a link, open a file, or perform some action

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality NoneNo confidentiality impact
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability NoneNo availability impact

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Questions about CVE-2018-20251

Is CVE-2018-20251 being exploited?
No exploitation is confirmed and no public exploit is known. EPSS puts the chance of exploitation in the next 30 days at 31%.
Which versions are affected by CVE-2018-20251?
WinRAR: before 5.70 Beta 1. WinRAR: All versions prior and including 5.61. Winrar: ≤ 5.61.
How do I fix or mitigate CVE-2018-20251?
The vendor has published a fix. The advisory is on securitylab.ru.

Last updated

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for WinRAR, not every advisory.