Skip to content

Cross-Site Request Forgery (CSRF) in trestle-auth

High severity GitHub Reviewed Published Apr 12, 2021 in TrestleAdmin/trestle-auth • Updated May 4, 2023

Package

bundler trestle-auth (RubyGems)

Affected versions

>= 0.4.0, < 0.4.2

Patched versions

0.4.2

Description

Impact

A vulnerability in trestle-auth versions 0.4.0 and 0.4.1 allows an attacker to create a form that will bypass Rails' built-in CSRF protection when submitted by a victim with a trestle-auth admin session. This potentially allows an attacker to alter protected data, including admin account credentials.

Patches

The vulnerability has been fixed in trestle-auth 0.4.2 released to RubyGems.

For more information

If you have any questions or comments about this advisory:

References

@spohlenz spohlenz published to TrestleAdmin/trestle-auth Apr 12, 2021
Reviewed Apr 13, 2021
Published to the GitHub Advisory Database Apr 13, 2021
Published by the National Vulnerability Database Apr 13, 2021
Last updated May 4, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

EPSS score

0.063%
(29th percentile)

Weaknesses

CVE ID

CVE-2021-29435

GHSA ID

GHSA-h8hx-2c5r-32cf

Source code

No known source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.