GHSA-96c6-m98x-hxjx json
Zend-Session session validation vulnerability
published 2y ago modified last yr.
- cvss
- 6.5
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
`Zend\Session` session validators do not work as expected if set prior to the start of a session.
For instance, the following test case fails (where $this->manager is an instance of `Zend\Session\SessionManager`): ``` $this ->manager ->getValidatorChain() ->attach('session.validate', array(new RemoteAddr(), 'isValid'));
$this->manager->start();
$this->assertSame( array( 'Zend\Session\Validator\RemoteAddr' =3D> '', ), $_SESSION['__ZF']['_VALID'] ); ``` The implication is that subsequent calls to `Zend\Session\SessionManager#start()` (in later requests, assuming a session was created) will not have any validator metadata attached, which causes any validator metadata to be re-built from scratch, thus marking the session as valid.
An attacker is thus able to simply ignore session validators such as `RemoteAddr` or `HttpUserAgent`, since the "signature" that these validators check against is not being stored in the session.
Patch / fix
- packagist zendframework/zend-session 2.2.9, 2.3.4
- github.com/zendframework/zend-session@05fa954 commit
- github.com/zendframework/zend-session@1272fc0 commit
- github.com/zendframework/zend-session@35014ab commit
- github.com/zendframework/zend-session@3b1a65b commit
- github.com/zendframework/zend-session@6a27a9f commit
- github.com/zendframework/zend-session@7c4b73d commit
- github.com/zendframework/zend-session@7fc94bd commit
- github.com/zendframework/zend-session@93b43aa commit
- github.com/zendframework/zend-session@9868f84 commit
- github.com/zendframework/zend-session@a3382bf commit
Is GHSA-96c6-m98x-hxjx in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | zendframework/zend-session | >=2.0.0, <2.2.9 >=2.3.0, <2.3.4 |
2.2.9 2.3.4 |
Classification
- Weakness
-
- CWE-384 Session Fixation
References
-
github.com
/zendframework/zend-session/commit/05fa95488b5ade513c4dcc56051a7ddb1c94f341
web
-
github.com
/zendframework/zend-session/commit/1272fc047121720130690c324413629d8f63d210
web
-
github.com
/zendframework/zend-session/commit/35014ab0ae17c2a169320f182697ee9fe73d841e
web
-
github.com
/zendframework/zend-session/commit/3b1a65b3193a4219f5c4259ab8735f9ad254a021
web
-
github.com
/zendframework/zend-session/commit/6a27a9fddd8f5b12b3af0de6309181ff5946dd0e
web
-
github.com
/zendframework/zend-session/commit/7c4b73dd64e01001946aac76c6deddfe1c6ef0be
web
-
github.com
/zendframework/zend-session/commit/7fc94bd6a60342416242a3899d63072c471b33d3
web
-
github.com
/zendframework/zend-session/commit/93b43aa0ca5348d29034f67195ffa3f4082878d5
web
-
github.com
/zendframework/zend-session/commit/9868f84513536446b0bac81cc95e0130b0a6fc9c
web
-
github.com
/zendframework/zend-session/commit/a3382bfd3067f527762294b5fc622550988e6862
web
-
github.com
/zendframework/zend-session/commit/b1903947e285568344b3458e4524b016ce311072
web
-
github.com
/zendframework/zend-session/commit/ff9236cc4c4944b5f5a6fbfee01420ef82c4fa91
web
-
framework.zend.com
/security/advisory/ZF2015-01
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/zendframework/zend-session/ZF2015-01.yaml
web
-
github.com
/zendframework/zend-session
package
Sources
- GitHub Advisory GHSA-96c6-m98x-hxjx
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.