GitHub Advisoryadvisory · Packagist

GHSA-jq87-2wxp-8349 ZendFramework Route Parameter Injection Via Query String in `Zend\Mvc`

HIGH Published 2024-06-07 Modified 2024-06-07 Official page ↗
Ecosystem
Packagist
Packages
zendframework/zendframework
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Weaknesses
CWE-74
Reviewed
2024-06-07

Affected packages

• Packagist zendframework/zendframework: >= 2.0.0, < 2.0.8 → fixed in 2.0.8 • Packagist zendframework/zendframework: >= 2.1.0, < 2.1.4 → fixed in 2.1.4

Description

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.

Related

Weakness · CWE (1)

  • CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component weakness

References