GHSA-jq87-2wxp-8349 json
ZendFramework Route Parameter Injection Via Query String in `Zend\Mvc`
published 2y ago modified last yr.
- cvss
- 7.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
In Zend Framework 2, `Zend\Mvc\Router\Http\Query` is used primarily to allow appending query strings to URLs when assembled. However, due to the fact that it captures any query parameters into the RouteMatch, and the fact that RouteMatch parameters are merged with any parent routes, this can lead to overriding already captured routing parameters, bypassing constraints defined in the parents.
As an example, consider the following route definition: ``` array( 'user' => array( 'type' => 'segment', 'options' => array( 'route' => '/user/:key', 'defaults' => array( 'controller' => 'UserController', 'action' => 'show-action', ), 'constraints' => array( 'key' => '[a-z0-9]+', ), ), 'child_routes' => array( 'query' => array('type' => 'query'), ), ), ) ``` If the request URI was /user/foo/?controller=SecretController&key=invalid_value, the RouteMatch returned after routing would contain the following: ``` array( 'controller' => 'SecretController', 'action' => 'show-action', 'key' => 'invalid_value', ) ``` This would lead to execution of a different controller than intended, with a value for the key parameter that bypassed the constraints outlined in the parent route.
Patch / fix
- packagist zendframework/zendframework 2.0.8, 2.1.4
Is GHSA-jq87-2wxp-8349 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 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | zendframework/zendframework | >=2.0.0, <2.0.8 >=2.1.0, <2.1.4 |
2.0.8 2.1.4 |
Classification
- Weakness
-
- CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component
References
-
github.com
/zendframework/zendframework/commit/0a7ec3407f02db29ea2ffd6daa71ead6fd151cfe
web
-
github.com
/zendframework/zendframework/commit/7fcb88ebc2d56f74aa943909f2b6b53f5c86b081
web
-
framework.zend.com
/security/advisory/ZF2013-01
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/zendframework/zendframework/ZF2013-01.yaml
web
-
github.com
/zendframework/zendframework
package
Sources
- GitHub Advisory GHSA-jq87-2wxp-8349
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.