Security
Headlines
HeadlinesLatestCVEs

Headline

CVE-2022-31072: Merge pull request #1446 from octokit/updates-release-steps-ic · octokit/octokit.rb@1c8edec

Octokit is a Ruby toolkit for the GitHub API. Versions 4.23.0 and 4.24.0 of the octokit gem were published containing world-writeable files. Specifically, the gem was packed with files having their permissions set to -rw-rw-rw- (i.e. 0666) instead of rw-r--r-- (i.e. 0644). This means everyone who is not the owner (Group and Public) with access to the instance where this release had been installed could modify the world-writable files from this gem. This issue is patched in Octokit 4.25.0. Two workarounds are available. Users can use the previous version of the gem, v4.22.0. Alternatively, users can modify the file permissions manually until they are able to upgrade to the latest version.

CVE
#git#ruby

@@ -2,16 +2,19 @@

  1. Create a list of all the changes since the prior release

  2. Compare the latest release to master using https://github.com/octokit/octokit.rb/compare/`${latest}`…master

  3. Open the linked pull requests from all the `Merge pull request #…` commits

  4. For all non-documentation PRs, copy title (including pull request number) into markdown list items

  5. (optional, but nice) Sort into logical buckets, like "support for additional endpoints", "enhancements", “bugfixes”

  6. Reorganize to put the pull request number at the start of the line

  7. Ensure there are no breaking changes _(if there are breaking changes you’ll need to create a release branch without those changes or bump the major version)_

  8. Update the version

  9. Open the linked pull requests from all the `Merge pull request #…` commits

  10. For all non-documentation PRs, copy title (including pull request number) into markdown list items

  11. (optional, but nice) Sort into logical buckets, like "support for additional endpoints", "enhancements", “bugfixes”

  12. Reorganize to put the pull request number at the start of the line

  13. Ensure there are no breaking changes _(if there are breaking changes you’ll need to create a release branch without those changes or bump the major version)_

  14. Update the version

  15. Update the constant in `lib/octokit/version.rb`

  16. Commit and push directly to master

  17. Run the `script/release` script to cut a release

  18. Draft a new release at https://github.com/octokit/octokit.rb/releases/new containing the curated changelog

  19. Commit the version change and push directly to master

  20. (Optional) Run `script/release` with no parameters to execute a dry run of a release

  21. Run the `script/release -r` script to cut a release (this will run `script/validate` to perform the permission check)

  22. Draft a new release at https://github.com/octokit/octokit.rb/releases/new containing the curated changelog

----

Prerequisites

Related news

GHSA-g28x-pgr3-qqx6: Octokit gem published with world-writable files

### Impact Versions [4.23.0](https://rubygems.org/gems/octokit/versions/4.23.0) and [4.24.0](https://rubygems.org/gems/octokit/versions/4.24.0) of the octokit gem were published containing world-writeable files. Specifically, the gem was packed with files having their permissions set to `-rw-rw-rw-` (i.e. 0666) instead of `rw-r--r--` (i.e. 0644). This means everyone who is not the owner (Group and Public) with access to the instance where this release had been installed could modify the world-writable files from this gem. Malicious code already present and running on your machine, separate from this package, could modify the gem’s files and change its behavior during runtime. ### Patches * [octokit 4.25.0](https://rubygems.org/gems/octokit/versions/4.25.0) ### Workarounds Users can use the previous version of the gem [v4.22.0](https://rubygems.org/gems/octokit/versions/4.22.0). Alternatively, users can modify the file permissions manually until they are able to upgrade to the la...

CVE: Latest News

CVE-2023-50976: Transactions API Authorization by oleiman · Pull Request #14969 · redpanda-data/redpanda
CVE-2023-6905
CVE-2023-6903
CVE-2023-6904
CVE-2023-3907