Skip to content
Fencer Vulns
medium 5.3

CVE-2018-7212 json

Sinatra Path Traversal vulnerability

published 2018-02-18 8 y ago modified 2026-06-17 4 mo ago also GHSA-h29f-7f56-j8wh , EUVD-2018-0167

cvss
5.3
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.8%
EPSS 1.8% chance of exploitation in 30 days, percentile 79%
public exploits
0
none known

Summary

An issue was discovered in rack-protection/lib/rack/protection/path_traversal.rb in Sinatra 2.x before 2.0.1 on Windows. Path traversal is possible via backslash characters.

Patch / fix

  • rubygems sinatra 2.0.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-7212 updated cvss 5.3

rubygem-sinatra: path traversal via backslash characters

  • Red Hat Enterprise Linux 6 pcs Red Hat Enterprise Linux 7 pcs, pcs-snmp, python-clufter Red Hat OpenStack Platform 10 (Newton) Operational Tools rubygem-sinatra Red Hat Satellite 6 rubygem-sinatra, tfm-ror51-rubygem-sinatra Red Hat Software Collections rh-ror50-rubygem-sinatra Red Hat Storage 3 rubygem-sinatra
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.84% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 5.3 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.0 5.3 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
rubygems sinatra
>=2.0.0.beta1, <2.0.1
2.0.1

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.