🚨 [security] Update capybara 3.7.1 → 3.39.2 (minor)

🚨 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?

✳️ capybara (3.7.1 → 3.39.2) · Repo · Changelog

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.

↗️ addressable (indirect, 2.5.2 → 2.8.4) · Repo · Changelog

Security Advisories 🚨

🚨 Regular Expression Denial of Service in Addressable templates

Release Notes

2.8.4 (from changelog)

2.8.3 (from changelog)

2.8.2 (from changelog)

2.8.1 (from changelog)

2.8.0 (from changelog)

2.7.0 (from changelog)

2.6.0 (from changelog)

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

↗️ mini_mime (indirect, 1.0.1 → 1.1.2) · Repo · Changelog

Commits

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

↗️ mini_portile2 (indirect, 2.3.0 → 2.8.2) · Repo · Changelog

Release Notes

2.8.2

2.8.1

2.8.0

2.7.1

2.7.0

2.6.1

2.6.0

2.5.3

2.5.2

2.5.1

2.5.0

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.

↗️ nokogiri (indirect, 1.8.4 → 1.15.2) · Repo · Changelog

Security Advisories 🚨

🚨 Update packaged libxml2 to v2.10.4 to resolve multiple CVEs

🚨 Unchecked return value from xmlTextReaderExpand

🚨 Nokogiri contains libxml Out-of-bounds Write vulnerability

🚨 libxslt Type Confusion vulnerability that affects Nokogiri

🚨 Improper Handling of Unexpected Data Type in Nokogiri

🚨 Integer Overflow or Wraparound in libxml2 affects Nokogiri

🚨 Inefficient Regular Expression Complexity in Nokogiri

🚨 Denial of Service (DoS) in Nokogiri on JRuby

🚨 Out-of-bounds Write in zlib affects Nokogiri

🚨 XML Injection in Xerces Java affects Nokogiri

🚨 Update packaged libxml2 (2.9.12 → 2.9.13) and libxslt (1.1.34 → 1.1.35)

🚨 Improper Restriction of XML External Entity Reference (XXE) in Nokogiri on JRuby

🚨 Update packaged dependency libxml2 from 2.9.10 to 2.9.12

🚨 Nokogiri::XML::Schema trusts input by default, exposing risk of an XXE vulnerability

🚨 xmlStringLenDecodeEntities in parser.c in libxml2 2.9.10 has an infinite loop in a certain end-of-file situation.

🚨 Nokogiri gem, via libxslt, is affected by multiple vulnerabilities

🚨 Nokogiri Command Injection Vulnerability

🚨 Nokogiri gem, via libxslt, is affected by improper access control vulnerability

🚨 Nokogiri gem, via libxml2, is affected by multiple vulnerabilities

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.

↗️ public_suffix (indirect, 3.0.3 → 5.0.1) · Repo · Changelog

Release Notes

5.0.1 (from changelog)

5.0.0 (from changelog)

4.0.7 (from changelog)

4.0.6 (from changelog)

4.0.5 (from changelog)

4.0.4 (from changelog)

4.0.3 (from changelog)

4.0.2 (from changelog)

4.0.1 (from changelog)

4.0.0 (from changelog)

3.1.1 (from changelog)

3.1.0 (from changelog)

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.

↗️ rack (indirect, 2.0.5 → 2.2.7) · Repo · Changelog

Security Advisories 🚨

🚨 Possible Denial of Service Vulnerability in Rack’s header parsing

🚨 Possible DoS Vulnerability in Multipart MIME parsing

🚨 Possible DoS Vulnerability in Multipart MIME parsing

🚨 Possible DoS Vulnerability in Multipart MIME parsing

🚨 Denial of service via header parsing in Rack

🚨 Denial of Service Vulnerability in Rack Content-Disposition parsing

🚨 Denial of service via multipart parsing in Rack

🚨 Denial of service via header parsing in Rack

🚨 Denial of Service Vulnerability in Rack Content-Disposition parsing

🚨 Denial of service via multipart parsing in Rack

🚨 Denial of Service Vulnerability in Rack Content-Disposition parsing

🚨 Denial of service via multipart parsing in Rack

🚨 Denial of service via header parsing in Rack

🚨 Possible shell escape sequence injection vulnerability in Rack

🚨 Denial of Service Vulnerability in Rack Multipart Parsing

🚨 Denial of Service Vulnerability in Rack Multipart Parsing

🚨 Possible shell escape sequence injection vulnerability in Rack

🚨 Denial of Service Vulnerability in Rack Multipart Parsing

🚨 Possible shell escape sequence injection vulnerability in Rack

🚨 Percent-encoded cookies can be used to overwrite existing prefixed cookie names

🚨 Percent-encoded cookies can be used to overwrite existing prefixed cookie names

🚨 Directory traversal in Rack::Directory app bundled with Rack

🚨 Directory traversal in Rack::Directory app bundled with Rack

🚨 Possible information leak / session hijack vulnerability

🚨 Possible XSS vulnerability in Rack

🚨 Possible DoS vulnerability in Rack

Release Notes

2.2.7

2.2.2 (from changelog)

2.2.1 (from changelog)

2.2.0 (from changelog)

2.1.2 (from changelog)

2.1.1 (from changelog)

2.1.0 (from changelog)

2.0.8 (from changelog)

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.

↗️ rack-test (indirect, 1.1.0 → 2.1.0) · Repo · Changelog

Release Notes

2.1.0 (from changelog)

2.0.2 (from changelog)

2.0.1 (from changelog)

2.0.0 (from changelog)

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.

↗️ xpath (indirect, 3.1.0 → 3.2.0) · Repo · Changelog

Commits

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

🆕 matrix (added, 0.4.2)

🆕 racc (added, 1.7.0)

🆕 regexp_parser (added, 2.8.1)

Depfu Status

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

isleofruby / isleofruby-activities