Reject private and special-use destination addresses before connection
A public-looking hostname resolves to an internal address during import and reaches a service unavailable to the user.
- Focused work estimate
- 4h + prerequisites
- Priority in the scenario
- Urgent
- Engineering practice
- Network security · SSRF prevention
Estimated field mix
- Security60%
- Networking40%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional knowledge service imports documents from customer-entered URLs. The importer follows redirects and trusts response metadata too broadly.
Setup prerequisites
- Build a local fetch adapter and controlled HTTP test servers.
- Use synthetic documents and deny network access outside the test allowlist.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Apply destination-address policy to every resolved connection target.
- Reject loopback, private and special-use addresses outside explicit local tests.
- Prevent resolver results from changing unchecked before connection.
Implementation constraints
- Use an injected resolver and connection adapter; tests never contact internal services.
Verification to include
- Resolve an allowed synthetic public address through the fixture adapter.
- Return loopback or changed resolution and verify no connection is opened.
Deliverables
- Resolver-to-connection policy and fixture tests
Rollout and recovery
Run policy checks before enabling network fetches; deny unresolved or ambiguous destinations.
Value of the work
For the engineer: Practice defensive URL handling and bounded untrusted-input processing.
For the team: Review whether integrations can import content without expanding infrastructure access.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.