CACrown ArchivesThe cinema collection
Menu
Research dossier · General Reference

FTP bounce attack

Open-knowledge reference entry

Cross-disciplinary reference desk with index cards, atlas, dictionary and catalogue
General referenceInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionSep 7, 2025
Entity authorityQ5427214
Source-derived summary

FTP bounce attack is an exploit of the FTP protocol whereby an attacker is able to use the PORT command to request access to ports indirectly through the use of the victim machine, which serves as a proxy for the request, similar to an Open mail relay using SMTP.

This technique can be used to port scan hosts discreetly, and to potentially bypass a network's access-control list to access specific ports that the attacker cannot access through a direct connection, for example with the nmap port scanner.

Nearly all modern FTP server programs are configured by default to refuse PORT commands that would connect to any host but the originating host, thwarting FTP bounce attacks.

Editorial summary

The public source identifies “FTP bounce attack” as open-knowledge reference entry. This brief keeps that definition visible, then builds a research path around bounce, attack and Open-knowledge.

Editorial reviewA practical starting point whose main value is the path it opens into stronger specialist and primary sources. The current 115-word lead offers orientation but no explicit four-digit date, so chronology should not be assumed. The selected authority fields contribute no independent date. Its value is orientation rather than verdict, with bounce, attack and Open-knowledge providing the first useful test.
Editorial analysis

Why this record matters

A short description can identify a subject without explaining its stakes. For “FTP bounce attack”, the useful work is to connect “open-knowledge reference entry” to the records capable of establishing context and consequence.

Evidence profile

Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Sep 7, 2025. The linked authority identifier is Q5427214. None of the 0 selected statements returned an explicit reference.

Critical limits

A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.

How to read it

Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.

Best used for
  • Subject orientation
  • Search vocabulary
  • Locating named sources
Verify next

The closest primary source, responsible institution and strongest cited specialist reference.

Three-step research path

  1. Establish the record: confirm the title “FTP bounce attack”, its source revision and the description used here.
  2. Expand the search: follow FTP bounce attack primary sources, FTP bounce attack archive and bounce research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “FTP bounce attack”?
  2. What terminology or title could unlock a more precise catalogue search?
  3. Which institution is responsible for the underlying evidence?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from FTP bounce attack” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.