excon vulnerabilities
EXtended http(s) CONnections
- Registry
- RubyGems
- Latest
- 1.12.0
- License
- MIT
2 known advisories
The latest version, 1.12.0, is not affected by any of them. Projects on older versions may be.
Update to the latest version:
bundle update --conservative excon # Gemfile: '>= 1.12.0'Is your project on an affected excon?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for excon
Excon does not redact additional sensitive/risky headers when following redirects
- Affected
- <1.5.0
- Fixed in
- 1.5.0
In RubyGem excon, interrupted Persistent Connections May Leak Response Data
- Affected
- <0.71.0
- Fixed in
- 0.71.0
Is your excon version vulnerable?
- excon 1.12No known advisories in 1.12.0
- excon 1.11No known advisories in 1.11.0
- excon 1.10No known advisories in 1.10.0
- excon 1.9No known advisories in 1.9.1
- excon 1.8No known advisories in 1.8.0
- excon 1.7No known advisories in 1.7.3
- excon 0.1121 advisory in 0.112.0
- excon 0.1111 advisory in 0.111.0
- excon 0.1101 advisory in 0.110.0
- excon 0.1091 advisory in 0.109.0
- excon 0.1081 advisory in 0.108.0
- excon 0.1071 advisory in 0.107.0
Which of your client projects still run an old excon?
NPMscan reads the Gemfile.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other RubyGems packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the RubyGems registry.