Skip to content

GHSA-4xq9-vw89-p5cx CVE-2013-7224

Fat Free CRM allows remote attackers to obtain sensitive information via a direct request

Medium RubyGems
Severity
Medium
The publisher's own rating, not a CVSS score
Exploit chance (EPSS)
2.53%
Chance of exploitation in the next 30 days. Higher than 84.88% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Fix
0.12.1
Upgrade fat_free_crm to this version or later

Description

Fat Free CRM before 0.12.1 does not restrict JSON serialization, which allows remote attackers to obtain sensitive information via a direct request, as demonstrated by a request for users/1.json.

Affected versions

RubyGems

PackageVulnerableFixed in
fat_free_crm
< 0.12.1
0.12.1

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.

fat_free_crm RubyGems → 0.12.1

bundler
bundle update fat_free_crm # Gemfile: gem "fat_free_crm", ">= 0.12.1"

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-9pm8-vwc5-w2hm
Fat Free CRM has BOLA in DELETE /emails/:id - Any authenticated user can hit this endpoint and delete emails by ID
Low Also affects fat_free_crm
GHSA-p75c-5x3h-cxcg
Fat Free CRM vulnerable to Remote Denial of Service via Tasks endpoint
Medium Also affects fat_free_crm
GHSA-mcvq-7xjq-46x6
Fat Free CRM contains Cross-site Request Forgery vulnerablilities
Medium Also affects fat_free_crm
GHSA-f25h-3mj6-4jpg
Fat Free CRM vulnerable to Exposure of Sensitive Information
Medium Also affects fat_free_crm
GHSA-g897-cgfc-7q8v
Fat Free CRM has fixed token value
Medium Also affects fat_free_crm
GHSA-9ggp-5rf4-x7q9
Fat Free CRM vulnerable to SQL Injection
Medium Also affects fat_free_crm
GHSA-wcfx-3m6v-4frg
Fat Free CRM subject to Cross-site Scripting
Medium Also affects fat_free_crm
GHSA-wx7c-8j35-mpg8
Fat Free CRM Cross-Site Request Forgery vulnerability
Medium Also affects fat_free_crm
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