Audit: Binding to all interfaces detected with hardcoded values BAN-B104
Possible binding to all interfaces.
65 'quiet': True,
66 'no_warnings': True,
67 'default_search': 'auto',
68 'source_address': '0.0.0.0', 69} 70FFMPEG_OPTIONS = {
71 'before_options': '-reconnect 1 -reconnect_streamed 1 -reconnect_delay_max 5',
72 'options': '-vn',Possible binding to all interfaces.
49 'quiet': True,
50 'no_warnings': True,
51 'default_search': 'auto',
52 'source_address': '0.0.0.0', 53 'extract_flat': 'in_playlist', 54} 55YTDL_OPTIONS = {
56 'format': 'bestaudio/best',
57 'extractaudio': True,
Description
Binding to all network interfaces can potentially open up a service to traffic on unintended interfaces, that may not be properly documented or secured. This can be prevented by changing the code so it explicitly only allows access from localhost.
When binding to 0.0.0.0, you accept incoming connections from anywhere. During development, an application may have security vulnerabilities making it susceptible to SQL injections and other attacks. Therefore when the application is not ready for production, accepting connections from anywhere can be dangerous.
It is recommended to use 127.0.0.1 or local host during development phase. This prevents others from targeting your application and executing SQL injections against your project.
Bad practice
s = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
s.bind(('0.0.0.0, 31137)) # Binding to all interfaces
Recommended
s = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
s.bind(('127.0.0.1', 31137)) # Binding to local host
```
References:
- OWASP Top 10 2021 Category A05 - Security Misconfiguration