-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
[Backport v2.7-branch] DNS parsing issues #82392
base: v2.7-branch
Are you sure you want to change the base?
Conversation
Edit: never mind, missed the created issue |
After that issue is resolved, I will rebase code to re-trigger CI. |
84936ba
to
0b7e8c5
Compare
@kartben - any idea why the doc build is failing in this PR? |
Will have a look (my) tomorrow -- prob need to "freeze" requirements-doc.txt a bit more than it currently is 🥶 |
If the packet parsing fails in dns_unpack_response_query(), then do not continue further but bail out early. Signed-off-by: Jukka Rissanen <[email protected]>
Make sure we test malformed packet parsing. Signed-off-by: Jukka Rissanen <[email protected]>
Make sure that when copying the qname, the source buffer is large enough for the data. Signed-off-by: Jukka Rissanen <[email protected]>
The dns_unpack_answer() did not check the length of the message properly which can cause out of bounds read. Signed-off-by: Jukka Rissanen <[email protected]>
Make sure we catch invalid answer during parsing. Signed-off-by: Jukka Rissanen <[email protected]>
0b7e8c5
to
262cd26
Compare
relevant issue -- pypa/setuptools#4478 |
Backport #82072 to v2.7
Fixes #82139