Skip to content
Log inStart free trial

GHSA-xrr6-3pc4-m447 CVE-2015-7577

Active Record Improper Access Control

Medium RubyGems
Severity
5.3 / 10
Medium · CVSS 3.0
Exploit chance (EPSS)
4.25%
Chance of exploitation in the next 30 days. Higher than 91.05% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-284 Improper Access Control
Fix
3.2.22.1
Upgrade activerecord to this version or later

Description

activerecord/lib/active_record/nested_attributes.rb in Active Record in Ruby on Rails 3.1.x and 3.2.x before 3.2.22.1, 4.0.x and 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, and 5.x before 5.0.0.beta1.1 does not properly implement a certain destroy option, which allows remote attackers to bypass intended change restrictions by leveraging use of the nested attributes feature.

Affected versions

RubyGems

PackageVulnerableFixed in
activerecord
>= 3.1.0, < 3.2.22.1
3.2.22.1
activerecord
>= 4.0.0, < 4.1.14.1
4.1.14.1
activerecord
>= 4.2.0, < 4.2.5.1
4.2.5.1
activerecord
>= 5.0.0.beta1, < 5.0.0.beta1.1
5.0.0.beta1.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.

activerecord RubyGems → 3.2.22.1

bundler
bundle update activerecord # Gemfile: gem "activerecord", ">= 3.2.22.1"

Severity breakdown

CVSS 3.0 5.3

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

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

Weakness

CWE-284: Improper Access Control

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

How to prevent it
  • Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
  • 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

Advisories

Other links

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-76r7-hhxj-r776
Active Record logging vulnerable to ANSI escape injection
Medium Also affects activerecord
GHSA-579w-22j4-4749
Denial of Service Vulnerability in ActiveRecord's PostgreSQL adapter
High Also affects activerecord
GHSA-hq7p-j377-6v63
SQL Injection Vulnerability via ActiveRecord comments
High Also affects activerecord
GHSA-3hhc-qp5v-9p2j
Active Record RCE bug with Serialized Columns
Critical Also affects activerecord
GHSA-f57c-hx33-hvh8
Active Record component in Ruby on Rails has a data-type injection vulnerability
Critical Also affects activerecord
GHSA-8hc4-xxm3-5ppp
Active Record subject to Regular Expression Denial-of-Service (ReDoS)
High Also affects activerecord
GHSA-xf96-32q2-9rw2
Rails ActiveRecord gem vulnerable to SQL injection
High Also affects activerecord
GHSA-jmm9-2p29-vh2w
activerecord vulnerable to SQL Injection
High Also affects activerecord
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