2417 matches found
CVE-2019-16779
In RubyGem excon before 0.71.0, 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...
CVE-2019-16779
In RubyGem excon before 0.71.0, 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...
Race condition
In RubyGem excon before 0.71.0, 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...
CVE-2019-16779
In RubyGem excon before 0.71.0, 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...
CVE-2019-16779 In RubyGem excon, interrupted Persistent Connections May Leak Response Data
In RubyGem excon before 0.71.0, 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...
CVE-2019-16779
In CVE-2019-16779, RubyGem excon before 0.71.0 contains a race condition on persistent connections where an interrupted connection can leave data on the socket, causing subsequent requests to return content from the previous response. This affects ruby-excon packages across multiple distributions...
CVE-2019-16779
In RubyGem excon before 0.71.0, 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...
GHSA-Q58G-455P-8VW9 In RubyGem excon, interrupted Persistent Connections May Leak Response Data
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,...
In RubyGem excon, interrupted Persistent Connections May Leak Response Data
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,...
CVE-2014-0241
rubygem-hammercliforeman: File /etc/hammer/cli.modules.d/foreman.yml world readable...
Design/Logic Flaw
rubygem-hammercliforeman: File /etc/hammer/cli.modules.d/foreman.yml world readable...
CVE-2014-0241
rubygem-hammercliforeman: File /etc/hammer/cli.modules.d/foreman.yml world readable...
CVE-2014-0241
CVE-2014-0241 concerns rubygem-hammer_cli_foreman where the file /etc/hammer/cli.modules.d/foreman.yml is world-readable, enabling a local user to read potentially sensitive configuration data (e.g., usernames or passwords) as the underlying issue. Public sources in the provided documents corrobo...
CVE-2014-0241: Insufficiently Protected Credentials
rubygem-hammercliforeman: File /etc/hammer/cli.modules.d/foreman.yml world readable...
PT-2019-7043
Name of the Vulnerable Software and Affected Versions rubygem-hammer cli foreman affected versions not specified Description The issue is related to a file permission problem, where the file /etc/hammer/cli.modules.d/foreman.yml is world readable. This could potentially allow unauthorized access ...
CVE-2013-4593
RubyGem omniauth-facebook has an access token security vulnerability...
CVE-2013-4593
RubyGem omniauth-facebook has an access token security vulnerability...
CVE-2013-4593
CVE-2013-4593 concerns the RubyGem omniauth-facebook. The connected sources describe a flaw where the access token can be transmitted via the URL, enabling a remote attacker to bypass authentication and impersonate another user. This results in an authentication bypass vulnerability within the om...
