Repository navigation
Don't block literal IPs for outbound domain blocking #397
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
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,9 @@ | ||
| # Outbound domain blocking caveat | ||
|
|
||
| Java's `InetAddress.getByName()` handles both DNS lookups and parsing IP addresses. For example, Tomcat calls it to check whether an incoming request came through a trusted load balancer or proxy, without opening an outbound connection. | ||
|
|
||
| To avoid blocking these checks, Zen for Java skips literal IPv4 and IPv6 addresses when enforcing outbound domain rules. It also omits them from outbound reporting unless it can link them to an HTTP request. | ||
|
|
||
| Requests made directly to an IP bypass "block new outbound connections" and explicit IP block entries. Named domains still follow your allow/block rules, and SSRF checks still run. | ||
|
|
||
| Other Zen agents report outbound HTTP(S) traffic to literal IPs and block unapproved IP destinations when "block new outbound connections" is enabled. We're working on closing this gap in Java without disrupting inbound IP parsing. |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔵 Low - Bracketed IPv6 URLs remain blocked in outbound lockdown
An application makes an HTTP(S) request to a literal IPv6 URL such as
http://[::1]:8080while new outbound connections are blocked.URLCollectorand the DNS advice preserve the bracketed host, butIPValidator.isIPdoes not accept brackets, soDNSRecordCollectorstill applies the unknown-host outbound rule and throwsBlockedOutboundException. This contradicts the PR's literal-IPv6 exemption and can prevent legitimate direct IPv6 connections from being made.Show fix
More info - Reply on this comment to give feedback or ignore the issue.