An adversary compares output from a target system to known indicators that uniquely identify specific details about the target. Most commonly, fingerprinting is done to determine operating system and application versions. Fingerprinting can be done passively as well as actively. Fingerprinting by itself is not usually detrimental to the target. However, the information gathered through fingerprinting often enables an adversary to discover existing weaknesses in the target.
|
|
| ID | CAPEC-224 |
| Latest Sync Date | 11/05/25 15:15:38 |
| Original ID | 224 |
| Abstraction | Meta |
| Status | Stable |
| Alternate Terms | |
| Likelihood Of Attack | High |
| Typical Severity | Very Low |
| Related Attack Patterns | |
| Execution Flow | |
| Prerequisites | ::A means by which to interact with the target system directly.:: |
| Skills Required | ::SKILL:Some fingerprinting activity requires very specific knowledge of how different operating systems respond to various TCP/IP requests. Application fingerprinting can be as easy as envoking the application with the correct command line argument, or mouse clicking in the appropriate place on the screen.:LEVEL:Medium:: |
| Resources Required | ::If on a network, the adversary needs a tool capable of viewing network communications at the packet level and with header information, like Mitmproxy, Wireshark, or Fiddler.:: |
| Indicators | |
| Consequences | ::SCOPE:Confidentiality:TECHNICAL IMPACT:Read Data:: |
| Mitigations | ::While some information is shared by systems automatically based on standards and protocols, remove potentially sensitive information that is not necessary for the application's functionality as much as possible.:: |
| Example Instances | |
| Related Weaknesses | ::200:: |
| Taxonomy Mappings | TAXONOMY NAME:WASC:ENTRY ID:45:ENTRY NAME:Fingerprinting:: |
| Notes | |