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

Report: DNS Cache Poisoning Attack #1889

Open
idealeer opened this issue Jan 2, 2025 · 3 comments
Open

Report: DNS Cache Poisoning Attack #1889

idealeer opened this issue Jan 2, 2025 · 3 comments

Comments

@idealeer
Copy link

idealeer commented Jan 2, 2025

We found that SmartDNS does not use randomization for the source port in DNS queries, which makes it susceptible to cache poisoning attacks.

@Ryu-Z
Copy link

Ryu-Z commented Jan 21, 2025

Use a fixed port?

@PikuZheng
Copy link
Contributor

Use a fixed port?

yes. only change port while reconnect

@pymumu
Copy link
Owner

pymumu commented Jan 21, 2025

Currently, only one port number will be used for communication, and no random port number be used.

The latest code adds some processing to determine the communication source IP, port, and destination IP port. If these IP/port are different, the data will be discarded, which can avoid some problems to a certain extent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants