Advisory

GHSA-jq87-2wxp-8349

Also known as: None

Summary

ZendFramework Route Parameter Injection Via Query String in Zend\Mvc

Details

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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2024-06-07 20:15 UTC
Modified
2024-12-04 05:39 UTC

Affected packages and fixes

zendframework/zendframework

Packagist · All systems

Affected

  • introduced 2.0.0, fixed 2.0.8 (ecosystem)

Fixed versions

2.0.8

Fix

The export has no generic command for this ecosystem.

zendframework/zendframework

Packagist · All systems

Affected

  • introduced 2.1.0, fixed 2.1.4 (ecosystem)

Fixed versions

2.1.4

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences