Skip to content

Updating activesupport, rest-client and oc-chef-pedant for CVE-2023-22796 - #343

Closed
johnmccrae wants to merge 13 commits into
mainfrom
jfm/chef-activesupport-update
Closed

johnmccrae wants to merge 13 commits into
mainfrom
jfm/chef-activesupport-update

Conversation

@johnmccrae

Copy link
Copy Markdown
Contributor

Description

Activesupport 7.1.3.2 is subject to a CVE. We're updating all the things here to get past CVE-2023-22796

Related Issue

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

  • I have read the CONTRIBUTING document.
  • I have run the pre-merge tests locally and they pass.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • If Gemfile.lock has changed, I have used --conservative to do it and included the full output in the Description above.
  • All new and existing tests passed.
  • All commits have been signed-off for the Developer Certificate of Origin.

Signed-off-by: John McCrae <john.mccrae@progress.com>
@johnmccrae
johnmccrae requested review from a team and jaymzh as code owners September 26, 2025 15:34
Signed-off-by: John McCrae <john.mccrae@progress.com>
Signed-off-by: John McCrae <john.mccrae@progress.com>
Signed-off-by: John McCrae <john.mccrae@progress.com>
Signed-off-by: John McCrae <john.mccrae@progress.com>
Signed-off-by: John McCrae <john.mccrae@progress.com>
Signed-off-by: John McCrae <john.mccrae@progress.com>
Signed-off-by: John McCrae <john.mccrae@progress.com>
Signed-off-by: John McCrae <john.mccrae@progress.com>
Signed-off-by: John McCrae <john.mccrae@progress.com>
Signed-off-by: John McCrae <john.mccrae@progress.com>
Signed-off-by: John McCrae <john.mccrae@progress.com>
Signed-off-by: John McCrae <john.mccrae@progress.com>
@sonarqubecloud

Copy link
Copy Markdown

@sonarqube-for-infrastructure-prod

Copy link
Copy Markdown

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@jaymzh

jaymzh commented Oct 29, 2025

Copy link
Copy Markdown
Collaborator

@johnmccrae - I nuked activesupport altogether. You can rebase this and it should get much easier.

Comment thread chef-zero.gemspec
# Activesupport 7.1.3.2 also has a CVE in it which requires an upgrade to 7.1.5.2. Activesupport 7.1.5 requires fiddle = 1.1.0, but Chef-19 requires fiddle >= 1.1.6.
# Also, fiddle is a built-in gem for Ruby 3.1 but is broken out into a separate gem starting in Ruby 3.2.
if Gem::Version.new(RUBY_VERSION) <= Gem::Version.new("3.1.7")
s.add_dependency "fiddle", "= 1.1.0"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you can't do an if statement in a gemspec

@tpowell-progress tpowell-progress Nov 3, 2025 •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

More specifically, since a gemspec is evaluated at gem build time, and chef-zero is included (at least by Chef) as a gem published to RubyGems, this dependency will match the setup of the machine that built the gem, not the setup of the machine including the gem. (We do have an if or two in gemspecs that aren't subject to this pitfall, regardless of how dubious the practice may be.) cc: @johnmccrae

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just recalled @jaymzh removed activesupport with #349 (and then need for this PR)

@tpowell-progress

Copy link
Copy Markdown
Contributor

#349 eliminates the need for this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants