🚨 [security] Update globalid: 1.0.0 → 1.0.1 (patch) #100

depfu · 2023-01-20T10:15:30Z

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

↗️ globalid (indirect, 1.0.0 → 1.0.1) · Repo · Changelog

Security Advisories 🚨

🚨 ReDoS based DoS vulnerability in GlobalID

There is a ReDoS based DoS vulnerability in the GlobalID gem. This
vulnerability has been assigned the CVE identifier CVE-2023-22799.

Versions Affected: >= 0.2.1
Not affected: < 0.2.1
Fixed Versions: 1.0.1

Impact

There is a possible DoS vulnerability in the model name parsing section
of the GlobalID gem. Carefully crafted input can cause the regular
expression engine to take an unexpected amount of time. All users running
an affected release should either upgrade or use one of the workarounds
immediately.

Workarounds

There are no feasible workarounds for this issue.

Release Notes

1.0.1

Possible ReDoS based DoS vulnerability in GlobalID

There is a ReDoS based DoS vulnerability in the GlobalID gem. This
vulnerability has been assigned the CVE identifier CVE-2023-22799.

Versions Affected: >= 0.2.1
Not affected: NOTAFFECTED
Fixed Versions: 1.0.1

Impact

There is a possible DoS vulnerability in the model name parsing section of the
GlobalID gem. Carefully crafted input can cause the regular expression engine
to take an unexpected amount of time. All users running an affected release
should either upgrade or use one of the workarounds immediately.

Releases

The FIXED releases are available at the normal locations.

Workarounds

There are no feasible workarounds for this issue.

Credits

Thank you ooooooo_k for reporting this!

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 2 commits:

↗️ concurrent-ruby (indirect, 1.1.9 → 1.2.2) · Repo · Changelog

Release Notes

1.2.2

concurrent-ruby 1.2.2:

(#993) Fix arguments passed to Concurrent::Map's default_proc.

1.2.1

concurrent-ruby 1.2.1:

(#990) Add missing require 'fiber' for FiberLocalVar.

(#989) Optimize Concurrent::Map#[] on CRuby by letting the backing Hash handle the default_proc.

1.2.0

concurrent-ruby 1.2.0:

(#975) Set the Ruby compatibility version at 2.3

(#962) Fix ReentrantReadWriteLock to use the same granularity for locals as for Mutex it uses.

(#983) Add FiberLocalVar

(#934) concurrent-ruby now supports requiring individual classes (public classes listed in the docs), e.g., require 'concurrent/map'

(#976) Let Promises.any_fulfilled_future take an Event

Improve documentation of various classes

(#972) Remove Rubinius-related code

concurrent-ruby-edge 0.7.0:

(#975) Set the Ruby compatibility version at 2.3

(#934) concurrent-ruby now supports requiring individual classes (public classes listed in the docs), e.g., require 'concurrent/map'

(#972) Remove Rubinius-related code

1.1.10

concurrent-ruby:

(#951) Set the Ruby compatibility version at 2.2

(#939, #933) The caller_runs fallback policy no longer blocks reads from the job queue by worker threads

(#938, #761, #652) You can now explicitly prune_pool a thread pool (Sylvain Joyeux)

(#937, #757, #670) We switched the Yahoo stock API for demos to Alpha Vantage (Gustavo Caso)

(#932, #931) We changed how SafeTaskExecutor handles local jump errors (Aaron Jensen)

(#927) You can use keyword arguments in your initialize when using Async (Matt Larraz)

(#926, #639) We removed timeout from TimerTask because it wasn't sound, and now it's a no-op with a warning (Jacob Atzen)

(#919) If you double-lock a re-entrant read-write lock, we promote to locked for writing (zp yuan)

(#915) monotonic_time now accepts an optional unit parameter, as Ruby's clock_gettime (Jean Boussier)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ i18n (indirect, 1.10.0 → 1.12.0) · Repo · Changelog

Release Notes

1.12.0

What's Changed

Revert "Add support for CLDR data in I18n::Backend::Pluralization" by @radar in #633 -- this was causing breaking changes unintentionally.

Full Changelog: v1.11.0...v1.12.0

1.11.0

What's Changed

Consistently return array from bulk lookup, even if translation(s) missing by @sambostock in #628

Fix typos by @movermeyer in #631

Add support for CLDR data in I18n::Backend::Pluralization by @movermeyer in #630

New Contributors

@sambostock made their first contribution in #628

Full Changelog: v1.10.0...v1.11.0

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 20 commits:

↗️ tzinfo (indirect, 2.0.4 → 2.0.6) · Repo · Changelog

Release Notes

2.0.6

Eliminate Object#untaint deprecation warnings on JRuby 9.4.0.0. #145.

TZInfo v2.0.6 on RubyGems.org

2.0.5

Changed DateTime results to always use the proleptic Gregorian calendar. This affects DateTime results prior to 1582-10-15 and any arithmetic performed on the results that would produce a secondary result prior to 1582-10-15.

Added support for eager loading all the time zone and country data by calling either TZInfo::DataSource#eager_load! or TZInfo.eager_load!. Compatible with Ruby On Rails' eager_load_namespaces. #129.

Ignore the SECURITY file from Arch Linux's tzdata package. #134.

TZInfo v2.0.5 on RubyGems.org

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 39 commits:

↗️ zeitwerk (indirect, 2.5.4 → 2.6.7) · Repo · Changelog

Release Notes

2.6.7 (from changelog)

Reset module state on Zeitwerk::NameError.

If an autoload is triggered, the file is loaded successfully, but the expected constant does not get defined, Ruby resets the state of the module. In particular, autoload? returns nil for that constant name, and constants does not include the constant name (starting with Ruby 3.1).

Zeitwerk is more strict, not defining the expected constant is an error condition and the loader raises Zeitwerk::NameError. But this happens during the require call and the exception prevents Ruby from doing that cleanup.

With this change, the parent module is left in a state that makes more sense and is consistent with what Ruby does.

A message is logged if an autoload did not define the expected constant.

When that happens, Zeitwerk::NameError is raised and you normally see the exception. But if the error is shallowed, and you are inspecting the logs to investigate something, this new message may be helpful.

By default, Zeitwerk::Loader#dirs filters ignored root directories out. Please, pass ignored: true if you want them included.

It is very strange to configure a root directory and also ignore it, the edge case is supported only for completeness. However, in that case, client code listing root directories rarely needs the ignored ones.

Documentation improvements.

Enforcement of private interfaces continues with another gradual patch.

2.6.6 (from changelog)

The new eager_load_namespace had a bug when eager loading certain namespaces with collapsed directories. This has been fixed.

2.6.5 (from changelog)

Controlled errors in a couple of situations:

Attempting to eager load or reload without previously invoking setup now raises Zeitwerk::SetupRequired.

The method Zeitwerk::Loader#push_dir raises Zeitwerk::Error if it gets an anonymous custom namespace.

These should be backwards compatible, because they raise in circumstances that didn't work anyway. The goal here is to provide a meaningful error upfront.

Enforcement of private interfaces continues with another gradual patch.

2.6.4 (from changelog)

Ruby does not have gem-level visibility, so sometimes you need things to be public for them to be accessible internally. But they do not belong to the public interface of the gem.

A method that is undocumented and marked as @private in the source code is clearly private API, regardless of its formal Ruby visibility.

This release starts a series of gradual patches in which private interface is enforced with stricter formal visibility.

2.6.3 (from changelog)

v2.6.2 introduced a regression in the logic that checks whether two loaders want to manage the same root directories. It has been fixed.

2.6.2 (from changelog)

Zeitwerk::Loader#load_file allows you to load an individual Ruby file. Check its documentation for details.

Zeitwerk::Loader#eager_load_dir allows you to eager load a directory, recursively. Check its documentation for details.

Zeitwerk::Loader#eager_load_namespace allows you to eager a namespace, recursively. Namespaces are global, this method loads only what the receiver manages from that namespace, if anything. Check its documentation for details.

Zeitwerk::Loader.eager_load_namespace broadcasts eager_load_namespace to all registered loaders. Check its documentation for details.

Documents shadowed files. They always existed, but were not covered by the documentation.

Other assorted documentation improvements.

2.6.1 (from changelog)

Zeitwerk::Loader#dirs allows you to instrospect the root directories configured in the receiver. Please check its documentation for details.

2.6.0 (from changelog)

Directories are processed in lexicographic order.

Different file systems may list directories in different order, and with this change we ensure that client code eager loads consistently across platforms, for example.

Before this release, subdirectories of root directories always represented namespaces (unless ignored or collapsed). From now on, to be considered namespaces they also have to contain at least one non-ignored Ruby file with extension .rb, directly or recursively.

If you know beforehand a certain directory or directory pattern does not represent a namespace, it is intentional and more efficient to tell Zeitwerk to ignore it.

However, if you don't do so and have a directory tasks that only contains Rake files, arguably that directory is not meant to represent a Ruby module. Before, Zeitwerk would define a top-level Tasks module after it; now, it does not.

This feature is also handy for projects that have directories with auxiliary resources mixed in the project tree in a way that is too dynamic for an ignore pattern to be practical. See #216.

In the unlikely case that an existing project has an empty directory for the sole purpose of defining a totally empty module (no code, and no nested classes or modules), such module has now to be defined in a file.

Directories are scanned again on reloads.

On setup, loaders created with Zeitwerk::Loader.for_gem issue warnings if lib has extra, non-ignored Ruby files or directories.

This is motivated by existing gems with directories under lib that are not meant to define Ruby modules, like directories for Rails generators, for instance.

This warning can be silenced in the unlikely case that the extra stuff is actually autoloadable and has to be managed by Zeitwerk.

Please, check the documentation for further details.

This method returns an instance of a private subclass of Zeitwerk::Loader now, but you cannot rely on the type, just on the interface.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@depfu rebase
Rebases against your default branch and redoes this update

@depfu recreate
Recreates this PR, overwriting any edits that you've made to it

@depfu merge
Merges this PR once your tests are passing and conflicts are resolved

@depfu close
Closes this PR and deletes the branch

@depfu reopen
Restores the branch and reopens this PR (if it's closed)

@depfu pause
Ignores all future updates for this dependency and closes this PR

@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR

@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com>

depfu bot added the depfu label Jan 20, 2023

depfu bot added 2 commits March 13, 2023 22:43

Update minitest: 5.15.0 → 5.18.0 (minor) (#103)

7396d94

Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com>

Update globalid to version 1.0.1

38d03b1

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

🚨 [security] Update globalid: 1.0.0 → 1.0.1 (patch) #100

🚨 [security] Update globalid: 1.0.0 → 1.0.1 (patch) #100

depfu bot commented Jan 20, 2023 •

edited

🚨 [security] Update globalid: 1.0.0 → 1.0.1 (patch) #100

Are you sure you want to change the base?

🚨 [security] Update globalid: 1.0.0 → 1.0.1 (patch) #100

Conversation

depfu bot commented Jan 20, 2023 • edited

What changed?

↗️ globalid (indirect, 1.0.0 → 1.0.1) · Repo · Changelog

Impact

Workarounds

Possible ReDoS based DoS vulnerability in GlobalID

Impact

Releases

Workarounds

Credits

↗️ concurrent-ruby (indirect, 1.1.9 → 1.2.2) · Repo · Changelog

↗️ i18n (indirect, 1.10.0 → 1.12.0) · Repo · Changelog

What's Changed

What's Changed

New Contributors

↗️ tzinfo (indirect, 2.0.4 → 2.0.6) · Repo · Changelog

↗️ zeitwerk (indirect, 2.5.4 → 2.6.7) · Repo · Changelog

2.6.7 (from changelog)

2.6.6 (from changelog)

2.6.5 (from changelog)

2.6.4 (from changelog)

2.6.3 (from changelog)

2.6.2 (from changelog)

2.6.1 (from changelog)

2.6.0 (from changelog)

depfu bot commented Jan 20, 2023 •

edited