CVE-2019-16782
published 2019-12-18CVE-2019-16782: There's a possible information leak / session hijack vulnerability in Rack (RubyGem rack). This vulnerability is patched in versions 1.6.12 and 2.0.8…
PriorityP433medium5.9CVSS 3.1
AVNACHPRNUINSUCHINAN
EPSS
3.69%
88.5th percentile
There's a possible information leak / session hijack vulnerability in Rack (RubyGem rack). This vulnerability is patched in versions 1.6.12 and 2.0.8. Attackers may be able to find and hijack sessions by using timing attacks targeting the session id. Session ids are usually stored and indexed in a database that uses some kind of scheme for speeding up lookups of that session id. By carefully measuring the amount of time it takes to look up a session, an attacker may be able to find a valid session id and hijack the session. The session id itself may be generated randomly, but the way the session is indexed by the backing store does not use a secure comparison.
Affected
8 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | ruby-rack | < ruby-rack 2.1.1-2 (bookworm) | ruby-rack 2.1.1-2 (bookworm) |
| fedoraproject | fedora | — | — |
| opensuse | leap | — | — |
| rack | rack | < 1.6.12 | 1.6.12 |
| rack | rack | >= 0 < 1.6.12 | 1.6.12 |
| rack | rack | >= 2.0.0 < 2.0.8 | 2.0.8 |
| rack | rack | >= 2.0.0 < 2.0.8 | 2.0.8 |
| rubyonrails | active_record_session_store | <= 1.1.3 | — |
CVSS provenance
nvdv3.15.9MEDIUMCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
nvdv2.04.3MEDIUMAV:N/AC:M/Au:N/C:P/I:N/A:N
ghsa5.9MEDIUM
osv5.9MEDIUM
vendor_debian6.3MEDIUM
vendor_redhat6.3MEDIUM
vendor_ubuntu6.3MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
ruby-rack vulnerabilities
osv·2022-12-13·CVSS 5.9
CVE-2019-16782 [MEDIUM] ruby-rack vulnerabilities
ruby-rack vulnerabilities
It was discovered that Rack insecurely handled session ids. An
unauthenticated remote attacker could possibly use this issue to perform
a timing attack and hijack sessions. (CVE-2019-16782)
It was discovered that Rack was incorrectly handling cookies during
parsing, not validating them or performing the necessary integrity checks.
An attacker could possibly use this issue to overwrite existing cookie
data and gain control over a remote system's behaviour. This issue only
affected Ubuntu 14.04 ESM. (CVE-2020-8184)
It was discovered that Rack was not properly parsing data when processing
multipart POST requests. If a user or automated system were tricked into
sending a specially crafted multipart POST request to an application using
Rack, a remote attacker could
OSV
Activerecord-session_store Vulnerable to Timing Attack
osv·2021-03-09·CVSS 5.9
CVE-2019-25025 [MEDIUM] Activerecord-session_store Vulnerable to Timing Attack
Activerecord-session_store Vulnerable to Timing Attack
The `activerecord-session_store` (aka Active Record Session Store) component through 1.1.3 for Ruby on Rails does not use a constant-time approach when delivering information about whether a guessed session ID is valid. Consequently, remote attackers can leverage timing discrepancies to achieve a correct guess in a relatively short amount of time. This is a related issue to CVE-2019-16782.
## Recommendation
This has been fixed in version 2.0.0. All users are advised to update to this version or later.
GHSA
Activerecord-session_store Vulnerable to Timing Attack
ghsa·2021-03-09·CVSS 5.9
CVE-2019-25025 [MEDIUM] CWE-208 Activerecord-session_store Vulnerable to Timing Attack
Activerecord-session_store Vulnerable to Timing Attack
The `activerecord-session_store` (aka Active Record Session Store) component through 1.1.3 for Ruby on Rails does not use a constant-time approach when delivering information about whether a guessed session ID is valid. Consequently, remote attackers can leverage timing discrepancies to achieve a correct guess in a relatively short amount of time. This is a related issue to CVE-2019-16782.
## Recommendation
This has been fixed in version 2.0.0. All users are advised to update to this version or later.
OSV
CVE-2019-25025: The activerecord-session_store (aka Active Record Session Store) component through 1
osv·2021-03-05·CVSS 5.9
CVE-2019-25025 [MEDIUM] CVE-2019-25025: The activerecord-session_store (aka Active Record Session Store) component through 1
The activerecord-session_store (aka Active Record Session Store) component through 1.1.3 for Ruby on Rails does not use a constant-time approach when delivering information about whether a guessed session ID is valid. Consequently, remote attackers can leverage timing discrepancies to achieve a correct guess in a relatively short amount of time. This is a related issue to CVE-2019-16782.
GHSA
Possible Information Leak / Session Hijack Vulnerability in Rack
ghsa·2019-12-18
CVE-2019-16782 [MEDIUM] CWE-203 Possible Information Leak / Session Hijack Vulnerability in Rack
Possible Information Leak / Session Hijack Vulnerability in Rack
There's a possible information leak / session hijack vulnerability in Rack. Attackers may be able to find and hijack sessions by using timing attacks targeting the session id. Session ids are usually stored and indexed in a database that uses some kind of scheme for speeding up lookups of that session id. By carefully measuring the amount of time it takes to look up a session, an attacker may be able to find a valid session id and hijack the session.
The session id itself may be generated randomly, but the way the session is indexed by the backing store does not use a secure comparison.
### Impact
The session id stored in a cookie is the same id that is used when querying the backing session storage engine. Most storage m
OSV
Possible Information Leak / Session Hijack Vulnerability in Rack
osv·2019-12-18
CVE-2019-16782 [MEDIUM] Possible Information Leak / Session Hijack Vulnerability in Rack
Possible Information Leak / Session Hijack Vulnerability in Rack
There's a possible information leak / session hijack vulnerability in Rack. Attackers may be able to find and hijack sessions by using timing attacks targeting the session id. Session ids are usually stored and indexed in a database that uses some kind of scheme for speeding up lookups of that session id. By carefully measuring the amount of time it takes to look up a session, an attacker may be able to find a valid session id and hijack the session.
The session id itself may be generated randomly, but the way the session is indexed by the backing store does not use a secure comparison.
### Impact
The session id stored in a cookie is the same id that is used when querying the backing session storage engine. Most storage m
OSV
CVE-2019-16782: There's a possible information leak / session hijack vulnerability in Rack (RubyGem rack)
osv·2019-12-18·CVSS 5.9
CVE-2019-16782 [MEDIUM] CVE-2019-16782: There's a possible information leak / session hijack vulnerability in Rack (RubyGem rack)
There's a possible information leak / session hijack vulnerability in Rack (RubyGem rack). This vulnerability is patched in versions 1.6.12 and 2.0.8. Attackers may be able to find and hijack sessions by using timing attacks targeting the session id. Session ids are usually stored and indexed in a database that uses some kind of scheme for speeding up lookups of that session id. By carefully measuring the amount of time it takes to look up a session, an attacker may be able to find a valid session id and hijack the session. The session id itself may be generated randomly, but the way the session is indexed by the backing store does not use a secure comparison.
Ubuntu
Rack vulnerabilities
vendor_ubuntu·2022-12-13·CVSS 6.3
CVE-2020-8184 [MEDIUM] Rack vulnerabilities
Title: Rack vulnerabilities
Summary: Several security issues were fixed in Rack.
It was discovered that Rack insecurely handled session ids. An
unauthenticated remote attacker could possibly use this issue to perform
a timing attack and hijack sessions. (CVE-2019-16782)
It was discovered that Rack was incorrectly handling cookies during
parsing, not validating them or performing the necessary integrity checks.
An attacker could possibly use this issue to overwrite existing cookie
data and gain control over a remote system's behaviour. This issue only
affected Ubuntu 14.04 ESM. (CVE-2020-8184)
It was discovered that Rack was not properly parsing data when processing
multipart POST requests. If a user or automated system were tricked into
sending a specially crafted multipart POST reques
Red Hat
rubygem-activerecord-session_store: hijack sessions by using timing attacks targeting the session id
vendor_redhat·2019-12-22·CVSS 6.3
CVE-2019-25025 [MEDIUM] CWE-200 rubygem-activerecord-session_store: hijack sessions by using timing attacks targeting the session id
rubygem-activerecord-session_store: hijack sessions by using timing attacks targeting the session id
The activerecord-session_store (aka Active Record Session Store) component through 1.1.3 for Ruby on Rails does not use a constant-time approach when delivering information about whether a guessed session ID is valid. Consequently, remote attackers can leverage timing discrepancies to achieve a correct guess in a relatively short amount of time. This is a related issue to CVE-2019-16782.
A flaw was found in the activerecord-session_store (Active Record Session Store) component through version 1.1.3 for Ruby on Rails where it does not use a constant time approach when delivering information about whether a guessed session ID is valid. This flaw allows remote attackers to leverage timing di
Red Hat
rubygem-rack: hijack sessions by using timing attacks targeting the session id
vendor_redhat·2019-12-18·CVSS 6.3
CVE-2019-16782 [MEDIUM] CWE-200 rubygem-rack: hijack sessions by using timing attacks targeting the session id
rubygem-rack: hijack sessions by using timing attacks targeting the session id
There's a possible information leak / session hijack vulnerability in Rack (RubyGem rack). This vulnerability is patched in versions 1.6.12 and 2.0.8. Attackers may be able to find and hijack sessions by using timing attacks targeting the session id. Session ids are usually stored and indexed in a database that uses some kind of scheme for speeding up lookups of that session id. By carefully measuring the amount of time it takes to look up a session, an attacker may be able to find a valid session id and hijack the session. The session id itself may be generated randomly, but the way the session is indexed by the backing store does not use a secure comparison.
A flaw was found in rubygem-rack in versions prior
Debian
CVE-2019-16782: ruby-rack - There's a possible information leak / session hijack vulnerability in Rack (Ruby...
vendor_debian·2019·CVSS 6.3
CVE-2019-16782 [MEDIUM] CVE-2019-16782: ruby-rack - There's a possible information leak / session hijack vulnerability in Rack (Ruby...
There's a possible information leak / session hijack vulnerability in Rack (RubyGem rack). This vulnerability is patched in versions 1.6.12 and 2.0.8. Attackers may be able to find and hijack sessions by using timing attacks targeting the session id. Session ids are usually stored and indexed in a database that uses some kind of scheme for speeding up lookups of that session id. By carefully measuring the amount of time it takes to look up a session, an attacker may be able to find a valid session id and hijack the session. The session id itself may be generated randomly, but the way the session is indexed by the backing store does not use a secure comparison.
Scope: local
bookworm: resolved (fixed in 2.1.1-2)
bullseye: resolved (fixed in 2.1.1-2)
forky: resolved (fixed in 2.1.1-2)
sid: re
No detection rules found.
No public exploits indexed.
arXiv
Microservice Vulnerability Analysis: A Literature Review with Empirical Insights
arxiv_fulltext·2024-07-31
Microservice Vulnerability Analysis: A Literature Review with Empirical Insights
Microservice Vulnerability Analysis: A Literature Review with Empirical Insights
Raveen Kanishka Jayalath*
University of Adelaide, Australia
[email protected]
Hussain Ahmad* *Authors contributed equally to this work. Corresponding author.
University of Adelaide, Australia
[email protected]
Diksha Goel
CSIRO's Data61, Australia
[email protected]
3cmMuhammad Shuja Syed
3cmSLB, USA
[email protected]
Faheem Ullah
University of Adelaide, Australia
[email protected]
plain
## Abstract
Microservice architectures are revolutionizing both small businesses and large corporations, igniting a new era of innovation with their exceptional advantages in maintainability, reusability, and scalability. However, these benefits come w
Bugzilla
CVE-2019-16782 rubygem-rack: hijack sessions by using timing attacks targeting the session id [epel-6]
bugzilla·2020-01-08·CVSS 6.3
CVE-2019-16782 [MEDIUM] CVE-2019-16782 rubygem-rack: hijack sessions by using timing attacks targeting the session id [epel-6]
CVE-2019-16782 rubygem-rack: hijack sessions by using timing attacks targeting the session id [epel-6]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-6.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
Discussion:
Use the following
Bugzilla
CVE-2019-16782 rubygem-rack: hijack sessions by using timing attacks targeting the session id
bugzilla·2020-01-08·CVSS 6.3
CVE-2019-16782 [MEDIUM] CVE-2019-16782 rubygem-rack: hijack sessions by using timing attacks targeting the session id
CVE-2019-16782 rubygem-rack: hijack sessions by using timing attacks targeting the session id
There's a possible information leak / session hijack vulnerability in Rack (RubyGem rack). This vulnerability is patched in versions 1.6.12 and 2.0.8. Attackers may be able to find and hijack sessions by using timing attacks targeting the session id. Session ids are usually stored and indexed in a database that uses some kind of scheme for speeding up lookups of that session id. By carefully measuring the amount of time it takes to look up a session, an attacker may be able to find a valid session id and hijack the session. The session id itself may be generated randomly, but the way the session is indexed by the backing store does not use a secure comparison.
Reference:
https://github.com/rack/
Bugzilla
CVE-2019-16782 rubygem-rack: hijack sessions by using timing attacks targeting the session id [fedora-all]
bugzilla·2020-01-08·CVSS 6.3
CVE-2019-16782 [MEDIUM] CVE-2019-16782 rubygem-rack: hijack sessions by using timing attacks targeting the session id [fedora-all]
CVE-2019-16782 rubygem-rack: hijack sessions by using timing attacks targeting the session id [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affect
Bugzilla
CVE-2019-16782 rubygem-rack: hijack sessions by using timing attacks targeting the session id [epel-7]
bugzilla·2020-01-08·CVSS 6.3
CVE-2019-16782 [MEDIUM] CVE-2019-16782 rubygem-rack: hijack sessions by using timing attacks targeting the session id [epel-7]
CVE-2019-16782 rubygem-rack: hijack sessions by using timing attacks targeting the session id [epel-7]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-7.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
Discussion:
Use the following
http://lists.opensuse.org/opensuse-security-announce/2020-02/msg00016.htmlhttp://www.openwall.com/lists/oss-security/2019/12/18/2http://www.openwall.com/lists/oss-security/2019/12/18/3http://www.openwall.com/lists/oss-security/2019/12/19/3http://www.openwall.com/lists/oss-security/2020/04/08/1http://www.openwall.com/lists/oss-security/2020/04/09/2https://github.com/rack/rack/commit/7fecaee81f59926b6e1913511c90650e76673b38https://github.com/rack/rack/security/advisories/GHSA-hrqr-hxpp-chr3https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HZXMWILCICQLA2BYSP6I2CRMUG53YBLX/http://lists.opensuse.org/opensuse-security-announce/2020-02/msg00016.htmlhttp://www.openwall.com/lists/oss-security/2019/12/18/2http://www.openwall.com/lists/oss-security/2019/12/18/3http://www.openwall.com/lists/oss-security/2019/12/19/3http://www.openwall.com/lists/oss-security/2020/04/08/1http://www.openwall.com/lists/oss-security/2020/04/09/2https://github.com/rack/rack/commit/7fecaee81f59926b6e1913511c90650e76673b38https://github.com/rack/rack/security/advisories/GHSA-hrqr-hxpp-chr3https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HZXMWILCICQLA2BYSP6I2CRMUG53YBLX/
2019-12-18
Published