-
Notifications
You must be signed in to change notification settings - Fork 899
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
Use yaml_unsafe_load to handle symbols #21988
Conversation
Prevent `Psych::DisallowedClass: Tried to load unspecified class: Symbol` while seeding due to the default change during the rails 6.0.5.1 release.
1dc36d0
to
d339213
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I can't believe this was changed in 6.0.5.1. 😭
Checked commit agrare@d339213 with ruby 2.6.9, rubocop 1.19.1, haml-lint 0.35.0, and yamllint |
Will this have to go back to najdorf for security reasons? |
The release was for a CVE so yes |
Backported to
|
Use yaml_unsafe_load to handle symbols (cherry picked from commit a4f4636)
Rails 6.0.5.1 changed the default behavior to use yaml safe load in 6.0.5.1 so we need to tell it use the old behavior in the dummy app. Related to the core change in: ManageIQ/manageiq#21988
Backported to
|
Use yaml_unsafe_load to handle symbols (cherry picked from commit a4f4636)
Prevent
Psych::DisallowedClass: Tried to load unspecified class: Symbol
while seeding due to the default change during the rails 6.0.5.1 release.https://discuss.rubyonrails.org/t/cve-2022-32224-possible-rce-escalation-bug-with-serialized-columns-in-active-record/81017#releases-2
NOTE the changelog has
config.active_storage.use_yaml_unsafe_load
but the actual config option isconfig.active_record.use_yaml_unsafe_load