[Snyk] Fix for 3 vulnerabilities

[samawad]

Snyk has created this PR to fix 3 vulnerabilities in the rubygems dependencies of this project.

Snyk changed the following file(s):

• Gemfile

⚠️ Warning

Failed to update the Gemfile.lock, please update manually before merging.

---

This upgrade contains major breaking changes for both Rails and Rack, requiring significant code and dependency updates. The Rails 3.0.6 → 5.0.0 upgrade is a multi-version jump with substantial API and pattern changes. The Rack 1.2.2 → 2.2.19 upgrade also introduces notable breaking changes to the core specification.

rails@3.0.6 → rails@5.0.0 (high):
This upgrade spans two major versions (3→4, 4→5) and requires a staged migration. Key breaking changes include the replacement of attr_accessible with the Strong Parameters pattern, a new requirement for Ruby 2.2.2+, and changes to controller parameter handling.

Highlights:

• Replace attr_accessible: Mass assignment protection via attr_accessible in models is removed. You must migrate to using Strong Parameters in controllers.
• Update Controller Params: ActionController::Parameters no longer inherits from HashWithIndifferentAccess, which may break code that treats the params object like a hash.
• Update Ruby Version: Rails 5.0 requires Ruby 2.2.2 or newer.

Source: Official Rails documentation
Recommendation: A staged upgrade (3.x → 4.2 → 5.0) is highly recommended to address breaking changes incrementally. Update gems and application code to use Strong Parameters before upgrading to Rails 4.

rack@1.2.2 → rack@2.2.19 (medium):
This major version upgrade introduces breaking changes to the Rack specification. Middleware may be affected by changes to how response bodies and request inputs are handled.

Highlights:

• Response Body Handling: Middleware can no longer assume the response body responds to #each. Streaming bodies that respond to #call are now supported.
• Input Stream: rack.input is no longer guaranteed to be rewindable.

Source: Rack Changelog
Recommendation: Review all custom middleware for compatibility with the Rack 2.x specification, particularly around response body iteration and input stream handling.

Notice 🤖: This content was generated using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

---

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-RUBY-RACK-13378928	721
	Allocation of Resources Without Limits or Throttling SNYK-RUBY-RACK-13378930	721
	Allocation of Resources Without Limits or Throttling SNYK-RUBY-RACK-13378932	721

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling