🚨 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.
Please note that this advisory only applies to the CRuby implementation
of Nokogiri, and only if the packaged libraries are being used. If
you've overridden defaults at installation time to use system libraries
instead of packaged libraries, you should instead pay attention to
your distro's libxml2 release announcements.
JRuby users are not affected.
Severity
The Nokogiri maintainers have evaluated this as Moderate.
Impact
From the CVE description, this issue applies to the xmlTextReader
module (which underlies Nokogiri::XML::Reader):
When using the XML Reader interface with DTD validation and
XInclude expansion enabled, processing crafted XML documents
can lead to an xmlValidatePopElement use-after-free.
Mitigation
Upgrade to Nokogiri ~> 1.15.6 or >= 1.16.2.
Users who are unable to upgrade Nokogiri may also choose a more
complicated mitigation: compile and link Nokogiri against patched
external libxml2 libraries which will also address these same issues.
Nokogiri v1.14.3 upgrades the packaged version of its dependency libxml2 to v2.10.4 from v2.10.3.
libxml2 v2.10.4 addresses the following known vulnerabilities:
CVE-2023-29469: Hashing of
empty dict strings isn't deterministic
CVE-2023-28484: Fix null deref
in xmlSchemaFixupComplexType
Schemas: Fix null-pointer-deref in xmlSchemaCheckCOSSTDerivedOK
Please note that this advisory only applies to the CRuby implementation of Nokogiri < 1.14.3,
and only if the packaged libraries are being used. If you've overridden defaults at installation
time to use system libraries instead of packaged libraries, you should instead pay attention to
your distro's libxml2 release announcements.
Mitigation
Upgrade to Nokogiri >= 1.14.3.
Users who are unable to upgrade Nokogiri may also choose a more complicated mitigation: compile
and link Nokogiri against external libraries libxml2 >= 2.10.4 which will also address these
same issues.
Impact
No public information has yet been published about the security-related issues other than the
upstream commits. Examination of those changesets indicate that the more serious issues relate to
libxml2 dereferencing NULL pointers and potentially segfaulting while parsing untrusted inputs.
New methods #lib_path and #include_path which point at the installed directories under ports. (by @flavorjones)
Add config param for CMAKE_BUILD_TYPE, which now defaults to Release. (#136 by @Watson1978)
Experimental
Introduce experimental support for MiniPortile#mkmf_config which sets up MakeMakefile variables to properly link against the recipe. This should make it easier for C extensions to package third-party libraries. (by @flavorjones)
With no arguments, will set up just $INCFLAGS, $libs, and $LIBPATH.
Optionally, if provided a pkg-config file, will use that config to more precisely set $INCFLAGS, $libs, $LIBPATH, and $CFLAGS/$CXXFLAGS.
Optionally, if provided the name of a static archive, will rewrite linker flags to ensure correct linkage.
Note that the behavior may change slightly before official support is announced. Please comment on #118 if you have feedback.
cmake: set CMAKE compile flags to configure cross-compilation similarly to autotools--host flag: SYSTEM_NAME, SYSTEM_PROCESSOR, C_COMPILER, and CXX_COMPILER. [#130] (Thanks, @stanhu!)
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 cancel merge
Cancels automatic merging of this PR
@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)
🚨 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?
↗️ nokogiri (indirect, 1.13.10 → 1.15.6) · Repo · Changelog
Security Advisories 🚨
🚨 Use-after-free in libxml2 via Nokogiri::XML::Reader
🚨 Update packaged libxml2 to v2.10.4 to resolve multiple CVEs
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
↗️ mini_portile2 (indirect, 2.8.0 → 2.8.5) · Repo · Changelog
Release Notes
2.8.5
2.8.4
2.8.3
2.8.2
2.8.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 49 commits:
version bump to 2.8.5
doc: update README with cmake_build_type documentation
Merge pull request #137 from flavorjones/flavorjones-update-gemspec
dev: gemspec has better desc and uses require_relative
Merge pull request #136 from Watson1978/release-build
Add config param for CMAKE_BUILD_TYPE
Create release binary with cmake explicitly
Merge pull request #135 from amatsuda/warning
warning: method redefined; discarding old source_directory=
version bump to v2.8.5.rc2
Merge pull request #134 from flavorjones/flavorjones-improve-mkmf-config-20230917
introduce the "static" parameter to mkmf_config
extract `lib_path` and `include_path` methods
version bump to v2.8.5.rc1
Merge pull request #133 from flavorjones/flavorjones-more-precise-pkg-config
feat: more precise implementation of mkmf_config for pkg-config
version bump to v2.9.0.rc1
Merge pull request #131 from flavorjones/118-fedora-pkgconf
feat: introduce MiniPortile.mkmf_config
test: add an example that uses MakeMakefile.pkg_config
ci: add a fedora job to the test suite
test: backfill coverage for MiniPortile#activate
Merge pull request #132 from flavorjones/flavorjones-uninitialized-ivar-warnings
fix: avoid uninitialized ivar warnings
version bump to v2.8.4
Merge pull request #130 from stanhu/sh-cmake-cross-compile-vars
version bump to v2.8.3
Remap x64 processor type to x86_64
[cmake] Automatically add required cross-compilation variables
Merge pull request #129 from stanhu/sh-cmake-msys
Update CHANGELOG.md
Add CHANGELOG.md for CMake fix
cmake: only use MSYS/NMake generators when available
version bump to v2.8.2
Merge pull request #126 from flavorjones/flavorjones-better-config-failure-log
convert source_directory into a posix path
omit misleading version number when using source_directory
feat: output complete logs on error, including "config.log"
Merge pull request #125 from petergoldstein/feature/add_ruby_3_2_to_ci
Adds Ruby 3.2 to CI. Updates checkout action version.
Merge pull request #124 from flavorjones/flavorjones-update-github-actions-v3
ci: update github actions to avoid node version warnings
version bump to v2.8.1
Merge pull request #122 from flavorjones/119-improve-patching
fix: handle patching in dirs that resemble an actual git dir
Merge pull request #121 from flavorjones/flavorjones-exercise-patching-in-examples
test: `rake test:examples` now exercises patching
Merge pull request #117 from flavorjones/flavorjones-loosen-bundler-dependency
dep(dev): loosen bundler dependency
↗️ racc (indirect, 1.6.1 → 1.7.3) · Repo · Changelog
Release Notes
1.7.3
1.7.2
1.7.1
1.7.0
1.6.2
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