Add nextjs-images-wildcard-hostname security rule #3700
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.
Summary
Adds a security rule to detect overly permissive wildcard hostnames in Next.js
images.remotePatternsconfiguration.Security Issue
Using
hostname: "**"in Next.js image configuration allows loading images from any domain, which can lead to:Solution
The rule detects wildcard hostname patterns and suggests using specific domains or more restrictive patterns.
Files Added
javascript/nextjs/security/nextjs-images-wildcard-hostname.yaml- Rule definitionjavascript/nextjs/security/nextjs-images-wildcard-hostname.js- Test casesMetadata
Test Coverage