LiveActive security incident?Get immediate response
CVE Record

CVE-2018-1000119: Sinatra rack-protection versions 1.5.4 and 2.0.0.rc3 and earlier contains a timing attack vulnerability in...

Sinatra rack-protection versions 1.5.4 and 2.0.0.rc3 and earlier contains a timing attack vulnerability in the CSRF token checking that can result in signatures can be exposed. This attack appear to be exploitable via network connectivity to the ruby application. This vulnerability appears to have been fixed in 1.5.5 and 2.0.0.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue affects older Sinatra rack-protection versions. A timing weakness in CSRF token comparison may let a network attacker infer token signature information. The sources name fixed versions, but provide no CVSS score or evidence of active exploitation.

Executive priority

Treat this as a moderate dependency remediation item. It affects web application trust controls, but the available sources do not show active exploitation or a critical severity score.

Technical view

CVE-2018-1000119 is a timing attack in CSRF token checking in rack-protection 1.5.4, 2.0.0.rc3, and earlier. The CVE says signatures can be exposed over network connectivity to the Ruby application. It was fixed in 1.5.5 and 2.0.0.

Likely exposure

Exposure is most likely in Ruby web applications using Sinatra or rack-protection versions at or below 1.5.4 or 2.0.0.rc3, especially where CSRF protection is enabled and the application is network reachable.

Exploitation context

The source bundle says exploitation appears possible via network connectivity to the Ruby application. It does not cite KEV listing, active exploitation, public exploit use, or observed attacks.

Researcher notes

The public record is sparse: no CVSS vector, CWE, or detailed exploitability analysis is included. Validate exact affectedness through dependency versions and vendor advisories, not CPE data, because the bundle lists affected vendor/product as unavailable.

Mitigation direction

  • Upgrade rack-protection to 1.5.5, 2.0.0, or later supported releases.
  • Apply relevant Red Hat or Debian security updates where packaged dependencies are used.
  • Check vendor guidance for affected distro package names and backported fixes.
  • Prioritize internet-facing Ruby applications that process authenticated form submissions.

Validation and detection

  • Inventory Sinatra and rack-protection versions in application dependency manifests and deployed artifacts.
  • Confirm whether distro packages include the referenced Red Hat or Debian security updates.
  • Identify applications using rack-protection CSRF checks and exposed over a network.
  • Run the existing application regression suite after dependency or package updates.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-1000119 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.