Описание
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.
| Релиз | Статус | Примечание |
|---|---|---|
| bionic | ignored | end of standard support, was needed |
| devel | not-affected | 2.1.1-4 |
| disco | ignored | end of life |
| eoan | ignored | end of life |
| esm-apps/bionic | released | 1.6.4-4ubuntu0.2+esm1 |
| esm-apps/focal | released | 2.0.7-2ubuntu0.1+esm1 |
| esm-apps/jammy | not-affected | 2.1.1-4 |
| esm-apps/xenial | released | 1.6.4-3ubuntu0.2+esm1 |
| esm-infra-legacy/trusty | released | 1.5.2-3+deb8u3ubuntu1~esm3 |
| focal | ignored | end of standard support, was needed |
Показывать по
Ссылки на источники
EPSS
4.3 Medium
CVSS2
6.3 Medium
CVSS3
Связанные уязвимости
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.
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.
There's a possible information leak / session hijack vulnerability in ...
Possible Information Leak / Session Hijack Vulnerability in Rack
EPSS
4.3 Medium
CVSS2
6.3 Medium
CVSS3