Bump nokogiri from 1.6.8.1 to 1.10.4
Created by: dependabot[bot]
Bumps nokogiri from 1.6.8.1 to 1.10.4.
Release notes
Sourced from nokogiri's releases.
1.10.4 / 2019-08-11
Security
#1915)
Address CVE-2019-5477 (A command injection vulnerability in Nokogiri v1.10.3 and earlier allows commands to be executed in a subprocess by Ruby's
Kernel.open
method. Processes are vulnerable only if the undocumented methodNokogiri::CSS::Tokenizer#load_file
is being passed untrusted user input.This vulnerability appears in code generated by the Rexical gem versions v1.0.6 and earlier. Rexical is used by Nokogiri to generate lexical scanner code for parsing CSS queries. The underlying vulnerability was addressed in Rexical v1.0.7 and Nokogiri upgraded to this version of Rexical in Nokogiri v1.10.4.
This CVE's public notice is sparklemotion/nokogiri#1915
1.10.3 / 2019-04-22
Security Notes
[MRI] Pulled in upstream patch from libxslt that addresses CVE-2019-11068. Full details are available in #1892. Note that this patch is not yet (as of 2019-04-22) in an upstream release of libxslt.
1.10.2 / 2019-03-24
Security
- [MRI] Remove support from vendored libxml2 for future script macros. #1871
- [MRI] Remove support from vendored libxml2 for server-side includes within attributes. #1877
Bug fixes
- [JRuby] Fix node ownership in duplicated documents. #1060
- [JRuby] Rethrow exceptions caught by Java SAX handler. [#1847, #1872] (Thanks, @adjam!)
1.10.1 / 2019-01-13
Features
- [MRI] During installation, handle Xcode 10's new library pathOS. [#1801, #1851] (Thanks, @mlj and @deepj!)
- Avoid unnecessary creation of
Proc
s in many methods. #1776 (Thanks, @chopraanmol1!)Bug fixes
... (truncated)
- CSS selector
:has()
now correctly matches against any descendant. Previously this selector matched against only direct children). #350 (Thanks, @Phrogz!)NodeSet#attr
now returnsnil
if it's empty. Previously this raised a NoMethodError.- [MRI] XPath errors are no longer suppressed during
XSLT::Stylesheet#transform
. Previously these errors were suppressed which led to silent failures and a subsequent segfault. #1802
Changelog
Sourced from nokogiri's changelog.
1.10.4 / 2019-08-11
Security
#1915)
Address CVE-2019-5477 (A command injection vulnerability in Nokogiri v1.10.3 and earlier allows commands to be executed in a subprocess by Ruby's
Kernel.open
method. Processes are vulnerable only if the undocumented methodNokogiri::CSS::Tokenizer#load_file
is being passed untrusted user input.This vulnerability appears in code generated by the Rexical gem versions v1.0.6 and earlier. Rexical is used by Nokogiri to generate lexical scanner code for parsing CSS queries. The underlying vulnerability was addressed in Rexical v1.0.7 and Nokogiri upgraded to this version of Rexical in Nokogiri v1.10.4.
This CVE's public notice is sparklemotion/nokogiri#1915
1.10.3 / 2019-04-22
Security Notes
[MRI] Pulled in upstream patch from libxslt that addresses CVE-2019-11068. Full details are available in #1892. Note that this patch is not yet (as of 2019-04-22) in an upstream release of libxslt.
1.10.2 / 2019-03-24
Security
- [MRI] Remove support from vendored libxml2 for future script macros. #1871
- [MRI] Remove support from vendored libxml2 for server-side includes within attributes. #1877
Bug fixes
- [JRuby] Fix node ownership in duplicated documents. #1060
- [JRuby] Rethrow exceptions caught by Java SAX handler. [#1847, #1872] (Thanks, @adjam!)
1.10.1 / 2019-01-13
Features
- [MRI] During installation, handle Xcode 10's new library path. [#1801, #1851] (Thanks, @mlj and @deepj!)
- Avoid unnecessary creation of
Proc
s in many methods. #1776 (Thanks, @chopraanmol1!)Bug fixes
- CSS selector
:has()
now correctly matches against any descendant. Previously this selector matched against only direct children). #350 (Thanks, @Phrogz!)NodeSet#attr
now returnsnil
if it's empty. Previously this raised a NoMethodError.- [MRI] XPath errors are no longer suppressed during
XSLT::Stylesheet#transform
. Previously these errors were suppressed which led to silent failures and a subsequent segfault. #1802... (truncated) 1.10.0 / 2019-01-04
Commits
-
beb832e
version bump to v1.10.4 -
5d30128
Merge branch '1915-css-tokenizer-load-file-vulnerability_v1.10.x' into v1.10.x -
c86b5fc
update CHANGELOG -
5fe449f
regenerate lexical scanner using rexical 1.0.7 -
6777008
eliminateeval
from Builder#initialize -
47a7bc7
rufo formatting -
094ecb1
rubocop security scan is run as part of thetest
rake target -
d068cd4
add rubocop as a dev dependency -
45ee92b
adding a temporary pipeline for v1.10.x -
8e24af5
version bump to v1.10.3 - Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebase
will rebase this PR -
@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it -
@dependabot merge
will merge this PR after your CI passes on it -
@dependabot squash and merge
will squash and merge this PR after your CI passes on it -
@dependabot cancel merge
will cancel a previously requested merge and block automerging -
@dependabot reopen
will reopen this PR if it is closed -
@dependabot ignore this [patch|minor|major] version
will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -
@dependabot use these labels
will set the current labels as the default for future PRs for this repo and language -
@dependabot use these reviewers
will set the current reviewers as the default for future PRs for this repo and language -
@dependabot use these assignees
will set the current assignees as the default for future PRs for this repo and language -
@dependabot use this milestone
will set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.