Prevent private octets from link collection for self-hosted #626
Conversation
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
collector/utils/url/index.jsThe function validURL(url) {
try {
const { protocol, hostname } = new URL(url);
if (!VALID_PROTOCOLS.includes(protocol)) return false;
if (isInvalidIp({ hostname })) return false;
return true;
} catch {}
return false;
} |
cabwds
pushed a commit
to cabwds/anything-llm
that referenced
this pull request
Jul 3, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Block private octets of link-scraping & collection just in case a user self-hosts AnythingLLM on the same network as another service that has zero authentication or access controls on it. Attackers in this case would also need to explicitly be granted high-level permissions to accomplish this in addition to knowing valid internal IPs.