LiveActive security incident?Get immediate response
CVE Record

CVE-2020-8166: A CSRF forgery vulnerability exists in rails < 5.2.5, rails < 6.0.4 that makes it possible for an attacker...

A CSRF forgery vulnerability exists in rails < 5.2.5, rails < 6.0.4 that makes it possible for an attacker to, given a global CSRF token such as the one present in the authenticity_token meta tag, forge a per-form CSRF token.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2020-8166 affects Ruby on Rails CSRF protections. Under specific conditions, an attacker with a global CSRF token could forge a per-form CSRF token, potentially causing a logged-in user to submit an unintended action. Impact is limited to integrity and requires user interaction.

Executive priority

Treat this as a moderate-priority framework security update. It is not described as actively exploited, but affected Rails applications may permit unauthorized authenticated changes if users are induced to interact with attacker-controlled content.

Technical view

Rails versions identified as vulnerable allow per-form CSRF token forgery when a global token, such as one exposed in an authenticity_token meta tag, is available. The CVSS 3.1 score is 4.3: network-reachable, low complexity, no privileges, user interaction required, integrity impact only.

Likely exposure

Exposure is most likely in Ruby on Rails applications running affected Rails versions and relying on Rails CSRF protections for state-changing form actions. Debian systems using vulnerable Rails packages may also be in scope per DSA-4766.

Exploitation context

The provided sources do not show active exploitation, and the CVE is not marked KEV. Exploitation requires user interaction and a usable global CSRF token. The issue is still relevant for applications where forged authenticated actions could alter sensitive records or workflows.

Researcher notes

Evidence is limited to the CVE description and linked advisories. The source bundle contains potentially inconsistent fixed-version wording, so verify exact affected and fixed releases against the Rails security post and downstream package advisory before closing findings.

Mitigation direction

  • Upgrade Rails to a fixed version cited by the Rails advisory or package vendor.
  • For Debian-managed deployments, apply the security update from DSA-4766.
  • Check vendor guidance if version ranges appear inconsistent across advisories.
  • Prioritize applications with authenticated state-changing workflows.
  • Review templates that expose global CSRF tokens in meta tags.

Validation and detection

  • Inventory Rails versions across production, staging, and build images.
  • Confirm whether Rails was updated to the advisory-fixed release line.
  • Identify apps using per-form CSRF tokens for sensitive actions.
  • Review dependency manifests and deployed package versions for vulnerable Rails releases.
  • Confirm Debian hosts have the relevant security package update installed.
Prepared
Confidence
medium
Sources
5

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.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
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-2020-8166 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
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

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

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.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2020-8166Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/ahttps://github.com/rails/railsFixed in 5.2.4.3, 6.0.3.1Listed
Weakness

CWE details

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

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.