-
-
Notifications
You must be signed in to change notification settings - Fork 220
Ten new vulnerabilities in Rack, GlobalID, and Rails this week #536
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@phillmv or @reedloden, I believe either of you can run the sync task? I don't have a GitHub Access Token setup to query GrapQL. :( I would rather not try to manually import 10 security advisories, if possible. |
Yup. Already in progress. Will have it finished and uploaded tonight after dinner. |
Fixed by 6a79ac9. |
Thank you! |
According to https://rubyonrails.org/2023/1/17/Rails-Versions-6-0-6-1-6-1-7-1-7-0-4-1-have-been-released these vulnerabilities have been fixed in Rails 6.0.6.1. However, |
@claasz not all of those CVEs were patched in 6.0.6.1. CVE-2023-22797 was fixed in |
When I run
in a Rails 6.0.6.1 application, I get
Do you think this is correct? Rails 6.0.6.1 still affected by these issues? |
complaining on actionpack 5.2.8.1 too |
Rails 6.0.Z and 5.2.Z are both unsupported / end-of-life, so please upgrade to a supported version. See https://guides.rubyonrails.org/maintenance_policy.html for more details. |
Not 100% correct. From the page you mention:
And please notice the fact that 6.0.6.1 was just released 3 days ago (https://rubyonrails.org/2023/1/17/Rails-Versions-6-0-6-1-6-1-7-1-7-0-4-1-have-been-released). |
I think it's still fair to say that Rails 6.0.Z is end-of-life, even if it still receiving updates for "severe security issues". It's clear that it is not receiving all security updates, so in my eyes (as a security professional/engineer), it might as well be fully end-of-life, as you're not receiving all the necessary fixes. :-) So, please upgrade. ❤️ |
For anybody wondering what's going on with Rails 6.0.Z: The confusion comes from Rails' release notes which could give you the impression that all of these CVEs have been fixed in 6.0.6.1 as well. Digging deeper into the security announcements and individual CHANGELOG files, situation looks like this:
|
@claasz also feel free to petition the Rails core team to release additional patches for the 6.0.x version family. It's ultimately there call when to drop support for a version family. We just collect the security advisory information. |
I just saw this stack of 10 new announcements over the past two days: https://discuss.rubyonrails.org/c/security-announcements/9
Usually, I rely on bundler-audit to tell me when there are new vulnerabilities, but in this case I happened to check the Rails security announcement page, saw these, and realized that bundler-audit was not telling me about them. That's when I came here.
All of these vulnerabilities definitely exist in the Github Advisory Database; maybe the
rake sync_github_advisories
task needs to be run?Also, much thanks for maintaining this repository; it's a lifesaver!
The text was updated successfully, but these errors were encountered: