Skip to content

Decidim vulnerable to sensitive data disclosure

High severity GitHub Reviewed Published Jul 11, 2023 in decidim/decidim • Updated Nov 6, 2023

Package

bundler decidim (RubyGems)

Affected versions

>= 0.27.0, < 0.27.3

Patched versions

0.27.3
bundler decidim-meetings (RubyGems)
>= 0.27.0, < 0.27.3
0.27.3

Description

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.

References

@andreslucena andreslucena published to decidim/decidim Jul 11, 2023
Published by the National Vulnerability Database Jul 11, 2023
Published to the GitHub Advisory Database Jul 11, 2023
Reviewed Jul 11, 2023
Last updated Nov 6, 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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
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:N/S:U/C:H/I:N/A:N

EPSS score

0.157%
(53rd percentile)

Weaknesses

CVE ID

CVE-2023-34090

GHSA ID

GHSA-jm79-9pm4-vrw9

Source code

Credits

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