Skip to content

GHSA-qcj6-vxwx-4rqv CVE-2024-27090

Decidim vulnerable to data disclosure through the embed feature

Medium RubyGems
Severity
0.0 / 10
Medium · CVSS 4.0
Exploit chance (EPSS)
0.49%
Chance of exploitation in the next 30 days. Higher than 42.28% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Fix
0.27.6
Upgrade decidim to this version or later

Description

Impact

If an attacker can infer the slug or URL of an unpublished or private resource, and this resource can be embedded (such as a Participatory Process, an Assembly, a Proposal, a Result, etc), then some data of this resource could be accessed.

Patches

version 0.27.6

https://github.com/decidim/decidim/commit/1756fa639ef393ca8e8bb16221cab2e2e7875705

Workarounds

Disallow access through your web server to the URLs finished with /embed.html

Affected versions

RubyGems

PackageVulnerableFixed in
decidim
< 0.27.6
0.27.6

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

decidim RubyGems → 0.27.6

bundler
bundle update decidim # Gemfile: gem "decidim", ">= 0.27.6"

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Attack vector
Network
Attack complexity
Low
Attack requirements
None
Privileges required
None
User interaction
None
Confidentiality (vulnerable system)
Low
Integrity (vulnerable system)
None
Availability (vulnerable system)
None
Confidentiality (subsequent systems)
None
Integrity (subsequent systems)
None
Availability (subsequent systems)
None

CVSS 3.1 5.3

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

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

Weakness

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How to prevent it
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-r3v7-5x4c-c69q
Decidim: JWT-backed authentication can be replayed across organizations
High Also affects decidim
GHSA-3cx6-j9j4-54mp
Decidim's private data exports can lead to data leaks
Medium Also affects decidim
GHSA-cc4g-m3g7-xmw8
Decidim has a cross-site scripting vulnerability in the version control page
High Also affects decidim
GHSA-vvqw-fqwx-mqmm
Decidim::Admin vulnerable to cross-site scripting (XSS) in the admin panel with QuillJS WYSWYG editor
Medium Also affects decidim
GHSA-7cx8-44pc-xv3q
Decidim cross-site scripting (XSS) in the pagination
High Also affects decidim
GHSA-9w99-78rj-hmxq
Cross-site scripting (XSS) in the dynamic file uploads
Medium Also affects decidim
GHSA-w3q8-m492-4pwp
Possibility to circumvent the invitation token expiry period
High Also affects decidim
GHSA-r275-j57c-7mf2
Race condition in Endorsements
Low Also affects decidim
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor