Information Disclosure in decidim (CVE-2023-34090)
Summary
Vulnerability in decidim (CVE-2023-34090). Confidential information can be exposed externally. Mitigation: upgrade to 0.27.3 or later.
Original description
The description as published by the source.
Note: added the actual report as a comment.
Summary
Decidim, a platform for digital citizen participation, uses a third-party library named Ransack for filtering certain database collections (e.g., public meetings). By default, this library allows filtering on all data attributes and associations. This allows an unauthenticated remote attacker to exfiltrate non-public data from the underlying database of a Decidim instance (e.g., exfiltrating data from the user table).
Impact
This issue may lead to Sensitive Data Disclosure.
Patches
The problem was patched in v0.27.3.
Workarounds
Disable or unpublish all meetings components from your application.
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-2023-34090 has been found in decidim.
Confidential information can be exposed externally.
What to do: upgrade decidim to 0.27.3 or later.
If unsure, ask your IT team or search "decidim CVE-2023-34090" on the vendor's site.
CVE-2023-34090 (decidim) — CWE-200
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.27.3 — apply immediately
Workaround: Disable or unpublish all meetings components from your application.
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.
Information disclosure (CWE-200) exists in decidim.
Check the vendor advisory for the affected versions of decidim.
Severity: ?. Confidential information can be exposed externally.
Update to 0.27.3.
Workaround: Disable or unpublish all meetings components from your application.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'decidim' . 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 'decidim' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
decidimを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Disable or unpublish all meetings components from your application.パッチが適用されるまでの応急処置として、Disable or unpublish all meetings components from your application. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade decidim to 0.27.3ステージング環境で 0.27.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com