Bumps excon from 0.62.0 to 0.71.0. This update includes a security fix.
Vulnerabilities fixed
*Sourced from The GitHub Security Advisory Database.*
> **Low severity vulnerability that affects excon**
> ### Impact
> There was a race condition around persistent connections, where a connection which is interrupted (such as by a timeout) would leave data on the socket. Subsequent requests would then read this data, returning content from the previous response. The race condition window appears to be short, and it would be difficult to purposefully exploit this.
>
> ### Patches
> The problem has been patched in 0.71.0, users should upgrade to this or a newer version (if one exists).
>
> ### Workarounds
> Users can workaround the problem by disabling persistent connections, though this may cause performance implications.
>
> ### References
> See the [patch](https://github.com/excon/excon/commit/ccb57d7a422f020dc74f1de4e8fb505ab46d8a29) for further details.
>
> ### For more information
> If you have any questions or comments about this advisory:
> * Open an issue in [excon/issues](https://github.com/excon/excon/issues)
> * Email us at [geemus+github@gmail.com](mailto:geemus+github@gmail.com)
>
> Affected versions: < 0.71.0
Changelog
*Sourced from [excon's changelog](https://github.com/excon/excon/blob/master/changelog.txt).*
> 0.71.0 2019-12-12
> =================
>
> fix for leftover data with interrupted persistent connections
>
> 0.70.0 2019-12-02
> =================
>
> Update bundled certificates
>
>
> 0.69.1 2019-11-21
> =================
>
> Fix mistake in proxy connection error handling
>
> 0.69.0 2019-11-21
> =================
>
> Raise better proxy connection errors
>
> 0.68.0 2019-10-25
> =================
>
> Updated bundled certs
>
> 0.67.0 2019-09-24
> =================
>
> Properly redact user/pass info from proxy credentials
> Update bundled certs
>
> 0.66.0 2019-08-06
> =================
>
> Add remote_ip to datum, enabling usage in middleware
> redirect follower now raises after following too many redirects (default 10)
> fixed stub clearing in tests to avoid race conditions
>
> 0.65.0 2019-07-22
> =================
>
> fix yardoc formatting
> fix creating Proc without a block
> reduce/refine gem file contents
> update bundled certs
> readd bundled certs to gem file contents
>
> 0.64.0 2019-04-15
> =================
> ... (truncated)
Commits
- [`1149d44`](https://github.com/excon/excon/commit/1149d44d921660bcde5e21671e6a10346d177f33) v0.71.0
- [`ccb57d7`](https://github.com/excon/excon/commit/ccb57d7a422f020dc74f1de4e8fb505ab46d8a29) fix for leftover data with interrupted persistent connections
- [`f8de8cf`](https://github.com/excon/excon/commit/f8de8cf63e789ff9329a13756bfb51364abe107a) v0.70.0
- [`93f4a21`](https://github.com/excon/excon/commit/93f4a214271df3b543ac4f4d1444d80ea2d75a01) v0.69.1
- [`e89bbb7`](https://github.com/excon/excon/commit/e89bbb718bb67972e2e08109fb4c1edd09568cd5) Merge pull request [#709](https://github-redirect.dependabot.com/excon/excon/issues/709) from jasquat/fix_response_status_check
- [`5647437`](https://github.com/excon/excon/commit/56474377bea9fdda2e07f52c169f4500e8c2be36) fixed response status check when making a request with a valid proxy is set
- [`f769176`](https://github.com/excon/excon/commit/f7691760969e74b6facaedd0a80ccef01709d428) v0.69.0
- [`20c0748`](https://github.com/excon/excon/commit/20c0748f2cfdd78a5f5b23057ad538240c372344) define ProxyConnectionError
- [`f44106a`](https://github.com/excon/excon/commit/f44106afd686d6eda076c0b92182f3df60e37f34) raise on failed proxy connect
- [`d7ed5fe`](https://github.com/excon/excon/commit/d7ed5fe894fb696fddb5f28c454c949d3c1116d9) be thorough in unsubscribing to notifications in instrumentation tests
- Additional commits viewable in [compare view](https://github.com/excon/excon/compare/v0.62.0...v0.71.0)
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.
If all status checks pass Dependabot will automatically merge this pull request.
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 close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor 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
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Pull request limits (per update run and/or open at any time)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)
Bumps excon from 0.62.0 to 0.71.0. This update includes a security fix.
Vulnerabilities fixed
*Sourced from The GitHub Security Advisory Database.* > **Low severity vulnerability that affects excon** > ### Impact > There was a race condition around persistent connections, where a connection which is interrupted (such as by a timeout) would leave data on the socket. Subsequent requests would then read this data, returning content from the previous response. The race condition window appears to be short, and it would be difficult to purposefully exploit this. > > ### Patches > The problem has been patched in 0.71.0, users should upgrade to this or a newer version (if one exists). > > ### Workarounds > Users can workaround the problem by disabling persistent connections, though this may cause performance implications. > > ### References > See the [patch](https://github.com/excon/excon/commit/ccb57d7a422f020dc74f1de4e8fb505ab46d8a29) for further details. > > ### For more information > If you have any questions or comments about this advisory: > * Open an issue in [excon/issues](https://github.com/excon/excon/issues) > * Email us at [geemus+github@gmail.com](mailto:geemus+github@gmail.com) > > Affected versions: < 0.71.0Changelog
*Sourced from [excon's changelog](https://github.com/excon/excon/blob/master/changelog.txt).* > 0.71.0 2019-12-12 > ================= > > fix for leftover data with interrupted persistent connections > > 0.70.0 2019-12-02 > ================= > > Update bundled certificates > > > 0.69.1 2019-11-21 > ================= > > Fix mistake in proxy connection error handling > > 0.69.0 2019-11-21 > ================= > > Raise better proxy connection errors > > 0.68.0 2019-10-25 > ================= > > Updated bundled certs > > 0.67.0 2019-09-24 > ================= > > Properly redact user/pass info from proxy credentials > Update bundled certs > > 0.66.0 2019-08-06 > ================= > > Add remote_ip to datum, enabling usage in middleware > redirect follower now raises after following too many redirects (default 10) > fixed stub clearing in tests to avoid race conditions > > 0.65.0 2019-07-22 > ================= > > fix yardoc formatting > fix creating Proc without a block > reduce/refine gem file contents > update bundled certs > readd bundled certs to gem file contents > > 0.64.0 2019-04-15 > ================= > ... (truncated)Commits
- [`1149d44`](https://github.com/excon/excon/commit/1149d44d921660bcde5e21671e6a10346d177f33) v0.71.0 - [`ccb57d7`](https://github.com/excon/excon/commit/ccb57d7a422f020dc74f1de4e8fb505ab46d8a29) fix for leftover data with interrupted persistent connections - [`f8de8cf`](https://github.com/excon/excon/commit/f8de8cf63e789ff9329a13756bfb51364abe107a) v0.70.0 - [`93f4a21`](https://github.com/excon/excon/commit/93f4a214271df3b543ac4f4d1444d80ea2d75a01) v0.69.1 - [`e89bbb7`](https://github.com/excon/excon/commit/e89bbb718bb67972e2e08109fb4c1edd09568cd5) Merge pull request [#709](https://github-redirect.dependabot.com/excon/excon/issues/709) from jasquat/fix_response_status_check - [`5647437`](https://github.com/excon/excon/commit/56474377bea9fdda2e07f52c169f4500e8c2be36) fixed response status check when making a request with a valid proxy is set - [`f769176`](https://github.com/excon/excon/commit/f7691760969e74b6facaedd0a80ccef01709d428) v0.69.0 - [`20c0748`](https://github.com/excon/excon/commit/20c0748f2cfdd78a5f5b23057ad538240c372344) define ProxyConnectionError - [`f44106a`](https://github.com/excon/excon/commit/f44106afd686d6eda076c0b92182f3df60e37f34) raise on failed proxy connect - [`d7ed5fe`](https://github.com/excon/excon/commit/d7ed5fe894fb696fddb5f28c454c949d3c1116d9) be thorough in unsubscribing to notifications in instrumentation tests - Additional commits viewable in [compare view](https://github.com/excon/excon/compare/v0.62.0...v0.71.0)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.If all status checks pass Dependabot will automatically merge this pull request.
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 close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor 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 - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)