Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uncaught exception in http.server request handling (<=3.10) #103223

Closed
kenballus opened this issue Apr 3, 2023 · 3 comments
Closed

Uncaught exception in http.server request handling (<=3.10) #103223

kenballus opened this issue Apr 3, 2023 · 3 comments
Labels
3.10 only security fixes stdlib Python modules in the Lib dir type-bug An unexpected behavior, bug, or error

Comments

@kenballus
Copy link
Contributor

kenballus commented Apr 3, 2023

Sending a null byte in an HTTP request path or URL triggers an uncaught ValueError in CPython 3.10 and below.

Reproduction Instructions

Open two terminals and do the following (requires python <=3.10; current 3.10 branch included):

Terminal 1:

$ ./python -m http.server --bind 127.0.0.1
Serving HTTP on 127.0.0.1 port 8000 (http://127.0.0.1:8000/) ...

Terminal 2:

$ printf 'GET \x00 HTTP/1.1\r\n\r\n' | nc localhost 8000

Terminal 1:

----------------------------------------
Exception occurred during processing of request from ('127.0.0.1', 56900)
Traceback (most recent call last):
  File "/home/bkallus/clones/cpython/Lib/socketserver.py", line 683, in process_request_thread
    self.finish_request(request, client_address)
  File "/home/bkallus/clones/cpython/Lib/http/server.py", line 1304, in finish_request
    self.RequestHandlerClass(request, client_address, self,
  File "/home/bkallus/clones/cpython/Lib/http/server.py", line 668, in __init__
    super().__init__(*args, **kwargs)
  File "/home/bkallus/clones/cpython/Lib/socketserver.py", line 747, in __init__
    self.handle()
  File "/home/bkallus/clones/cpython/Lib/http/server.py", line 433, in handle
    self.handle_one_request()
  File "/home/bkallus/clones/cpython/Lib/http/server.py", line 421, in handle_one_request
    method()
  File "/home/bkallus/clones/cpython/Lib/http/server.py", line 672, in do_GET
    f = self.send_head()
  File "/home/bkallus/clones/cpython/Lib/http/server.py", line 727, in send_head
    f = open(path, 'rb')
ValueError: embedded null byte
----------------------------------------

This bug is fixed in python 3.11+, but I haven't yet figured out why. As far as I can tell, the relevant portions of Lib/http/server.py and Lib/socketserver.py remain unchanged. I think the issue boils down to catching only OSErrors, but not ValueErrors, even though open can raise ValueErrors. I would guess that this happened because the docs do not clearly state that open(path, 'rb') can raise a ValueError.

Environment:

Arch Linux, x86_64
Python 3.10.10+

@kenballus kenballus added the type-bug An unexpected behavior, bug, or error label Apr 3, 2023
@kenballus kenballus changed the title Uncaught exception in http.server request handling (<=3.10 branch) Uncaught exception in http.server request handling (<=3.10) Apr 3, 2023
@arhadthedev arhadthedev added stdlib Python modules in the Lib dir 3.10 only security fixes labels Apr 4, 2023
@CCLDArjun
Copy link
Contributor

CCLDArjun commented Apr 4, 2023

did some debugging:

looks like translate_path() in send_head() in 3.10 returns the path with a null character at the end, whereas in 3.11, it doesn't. Since in translate_path():

path = posixpath.normpath(path)

is called. the behavior of posixpath.normpath varies in 3.10 and 3.11:

python3.11 -c "import pathlib; print(ord(pathlib.posixpath.normpath('\x00')))"
46

python3.10 -c "import pathlib; print(ord(pathlib.posixpath.normpath('\x00')))"
0

We error on this line in 3.10 because open() doesn't like null characters in the file path

f = open(path, 'rb')

So, should we catch the ValueError, like @kenballus suggested? Unsure whether either of the posixpath.normpath()s are broken, but it's suspicious that they're returning different values.

@iritkatriel
Copy link
Member

3.10 is in security-fix only mode now, so this is out of date.

@iritkatriel iritkatriel closed this as not planned Won't fix, can't repro, duplicate, stale Apr 5, 2023
@kenballus
Copy link
Contributor Author

kenballus commented Apr 5, 2023

Oops! Was going based on the chart on python.org and didn't notice that 3.10.11 came out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.10 only security fixes stdlib Python modules in the Lib dir type-bug An unexpected behavior, bug, or error
Projects
None yet
Development

No branches or pull requests

4 participants