diff options
author | Andrew Clayton <a.clayton@nginx.com> | 2022-11-07 00:06:43 +0000 |
---|---|---|
committer | Andrew Clayton <a.clayton@nginx.com> | 2023-01-12 17:56:01 +0000 |
commit | 97caab0e7a40c4034888e3269cdcbb858e47b45b (patch) | |
tree | 36001a6f6d125f07a91b47467bf01d3578942003 /docs | |
parent | 2c7e1bb92f6a3091b8fab872b93fa4791fbe14c8 (diff) | |
download | unit-97caab0e7a40c4034888e3269cdcbb858e47b45b.tar.gz unit-97caab0e7a40c4034888e3269cdcbb858e47b45b.tar.bz2 |
PHP: Fix a potential problem parsing the path.
@dward on GitHub reported an issue with a URL like
http://foo.bar/test.php?blah=test.php/foo
where we would end up trying to run the script
test.php?blah=test.php
In the PHP module the format 'file.php/' is treated as a special case in
nxt_php_dynamic_request() where we check the _path_ part of the url for
the string '.php/'.
The problem is that the path actually also contains the query string,
thus we were finding 'test.php/' in the above URL and treating that
whole path as the script to run.
The fix is simple, replace the strstr(3) with a memmem(3), where we can
limit the amount of path we use for the check.
The trick here and what is not obvious from the code is that while
path.start points to the whole path including the query string,
path.length only contains the length of the _path_ part.
NOTE: memmem(3) is a GNU extension and is neither specified by POSIX or
ISO C, however it is available on a number of other systems, including:
FreeBSD, OpenBSD, NetBSD, illumos, and macOS.
If it comes to it we can implement a simple alternative for systems
which lack memmem(3).
This also adds a test case (provided by @dward) to cover this.
Closes: <https://github.com/nginx/unit/issues/781>
Cc: Andrei Zeliankou <zelenkov@nginx.com>
Reviewed-by: Alejandro Colomar <alx@nginx.com>
Reviewed-by: Andrei Zeliankou <zelenkov@nginx.com> [test]
Signed-off-by: Andrew Clayton <a.clayton@nginx.com>
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions