-
Notifications
You must be signed in to change notification settings - Fork 494
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
Strange Behavior When Unpickling #1081
Comments
Here is the output from @TheTechromancer 's PoC:
Attached the pcap |
The payload value of an EDNS0 OPT record is stored in its class, and it seems to be having trouble unpickling the dns.rdataclass.RdataClass. I cannot reproduce this with Python 3.12.3. There were regressions involving various aspects of enums on some 3.11 releases before 3.11.5, and also with some 3.12 prereleases. See #972 and also probably more specifically this CPython issue. I'm betting your Python version is 3.11.3 or 3.11.4 but I can't tell from your report. If running on a newer CPython doesn't fix it, can you tell me what version of dnspython you're using as well? |
Wow, you're right. Updating to 3.11.5 fixed it. Thanks for your help! |
Hi, first off thanks for making such a useful library and for your quick responses in the past. This specific bug may not be in dnspython, but I'm still in the process of troubleshooting and hoping you might be able to shed some light on it:
This bug only triggers in very rare cases when an answer object is deserialized via
pickle.loads()
.We've only been able to reproduce it on Synack's internal infrastructure, which only adds to the strangeness. It seems to be dependent on the DNS server. The following code triggers the error (only on Synack's internal DNS):
@liquidsec can you post the wireshark capture?
The text was updated successfully, but these errors were encountered: