Cross-Site Request Forgery (CSRF) in trestle-auth (CVE-2021-29435)
Summary
Vulnerability in trestle-auth (CVE-2021-29435). Data can be tampered with by attackers. Mitigation: upgrade to 0.4.2 or later.
Original description
The description as published by the source.
trestle-auth is an authentication plugin for the Trestle admin framework. 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. The vulnerability has been fixed in trestle-auth 0.4.2 released to RubyGems.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-29435 has been found in trestle-auth.
Data can be tampered with by attackers.
What to do: upgrade trestle-auth to 0.4.2 or later.
If unsure, ask your IT team or search "trestle-auth CVE-2021-29435" on the vendor's site.
CVE-2021-29435 (trestle-auth) — CWE-352
Attack vector: remote (network-reachable) / unauthenticated
Patched: 0.4.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
CSRF (CWE-352) exists in trestle-auth.
Check the vendor advisory for the affected versions of trestle-auth.
Severity: ?. Data can be tampered with by attackers.
Update to 0.4.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'trestle-auth' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'trestle-auth' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
trestle-authを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade trestle-auth to 0.4.2ステージング環境で 0.4.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory rubygems.org
- patch github.com
- web github.com