add outbound blocking

[bitterpanda63]

Summary by Aikido

⚡ Enhancements

• Added domain-based outbound blocking and service config integration
• Reported and blocked hostnames before DNS resolution in socket sink

🔧 Refactors

• Removed hostname caching from SSRF vulnerability scan path

[aikido-pr-checks]

update_domains mutates self.domains (a shared dict) without synchronization; concurrent readers may observe partial updates or race conditions.

Details

✨ AI Reasoning
​ServiceConfig gained mutable fields domains and block_new_outgoing_requests that are written by update_service_config and read by sinks. The methods update_domains and set_block_new_outgoing_requests mutate shared ServiceConfig state without any synchronization or atomic swap, introducing a data race between writer and readers.

🔧 How do I fix it?
Use locks, concurrent collections, or atomic operations when accessing shared mutable state. Avoid modifying collections during iteration. Use proper synchronization primitives like mutex, lock, or thread-safe data structures.

_{More info - Comment @AikidoSec feedback: [FEEDBACK] to get better review comments in the future.}

[aikido-pr-checks]

Modifies shared collection cache.hostnames (cache.hostnames.add) without synchronization; this mutates shared state and can cause races or iteration errors.

Details

✨ AI Reasoning
​The new function report_and_check_hostname retrieves a shared thread-local/global cache via get_cache() and calls cache.hostnames.add(hostname, port) (line 18). This is a mutation of shared mutable state. There's no locking or atomic API shown, and other threads may concurrently access or iterate the same hostnames collection, risking race conditions or runtime errors (e.g., mutation during iteration). The change moved hostname registration earlier (it used to be added in vulnerabilities.init but that code was removed), so this PR introduced the new mutation point.

🔧 How do I fix it?
Use locks, concurrent collections, or atomic operations when accessing shared mutable state. Avoid modifying collections during iteration. Use proper synchronization primitives like mutex, lock, or thread-safe data structures.

_{More info - Comment @AikidoSec feedback: [FEEDBACK] to get better review comments in the future.}