GHSA-wx7c-8j35-mpg8 CVE-2015-1585
Fat Free CRM Cross-Site Request Forgery vulnerability
Medium
RubyGems
- Severity
- Medium
- The publisher's own rating, not a CVSS score
- Exploit chance (EPSS)
- 1.09%
- Chance of exploitation in the next 30 days. Higher than 65.52% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-352 Cross-Site Request Forgery (CSRF)
- Fix
0.13.6- Upgrade fat_free_crm to this version or later
Description
Fat Free CRM before 0.13.6 allows remote attackers to conduct cross-site request forgery (CSRF) attacks via a request without the authenticity_token, as demonstrated by a crafted HTML page that creates a new administrator account.
Affected versions
RubyGems
| Package | Vulnerable | Fixed in |
|---|---|---|
| fat_free_crm | < 0.13.6 |
0.13.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.
fat_free_crm RubyGems → 0.13.6
- bundler
bundle update fat_free_crm # Gemfile: gem "fat_free_crm", ">= 0.13.6"
Weakness
CWE-352: Cross-Site Request Forgery (CSRF)
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
How to prevent it
- Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. For example, use anti-CSRF packages such as the OWASP CSRFGuard. [REF-330] Another example is the ESAPI Session Management control, which includes a component for CSRF. [REF-45]
- Implementation: Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
- Architecture and Design: Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330). [REF-332]
- Architecture and Design: Identify especially dangerous operations. When the user performs a dangerous operation, send a separate confirmation request to ensure that the user intended to perform that operation.
- Architecture and Design: Use the "double-submitted cookie" method as described by Felten and Zeller: When a user visits a site, the site should generate a pseudorandom value and set it as a cookie on the user's machine. The site should require every form submission to include this value as a form value and also as a cookie value. When a POST request is sent to the site, the request should only be considered valid if the form value and the cookie value are the same. Because of the same-origin policy, an attacker cannot read or modify the value stored in the cookie. To successfully submit a form on behalf of the user, the attacker would have to correctly guess the pseudorandom value. If the pseudorandom value is cryptographically strong, this will be prohibitively difficult. This technique requires Javascript, so it may not work for browsers that have Javascript disabled. [REF-331]
- Architecture and Design: Do not use the GET method for any request that triggers a state change.
- Implementation: Check the HTTP Referer header to see if the request originated from an expected page. This could break legitimate functionality, because users or proxies may have disabled sending the Referer for privacy reasons.
References
Advisories
Packages
Other links
- github.com/fatfreecrm/fat_free_crm/commit/86fd7f98c9583fd36384987282d1c086fdcecd7c
- exchange.xforce.ibmcloud.com/vulnerabilities/100925
- github.com/fatfreecrm/fat_free_crm/wiki/CSRF-Vulnerability-%28CVE-2015-1585%29
- github.com/rubysec/ruby-advisory-db/blob/master/gems/fat_free_crm/CVE-2015-1585…
- packetstormsecurity.com/files/130410/Fat-Free-CRM-0.13.5-Cross-Site-Request-Forgery.html
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why 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-4xq9-vw89-p5cx Fat Free CRM allows remote attackers to obtain sensitive information via a direct request | Medium | Also affects fat_free_crm |
| GHSA-wcfx-3m6v-4frg Fat Free CRM subject to Cross-site Scripting | Medium | Also affects fat_free_crm |
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