CAPECattack pattern

CAPEC-224 Fingerprinting

Very Low Official page ↗
Abstraction
Meta
Status
Stable
Likelihood of attack
High
Typical severity
Very Low
CAPEC version
3.9

Description

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.

Prerequisites

• A means by which to interact with the target system directly.

Skills required

• [Medium] 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.

Consequences

• Confidentiality: 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.

Related

Weakness · CWE (1)

  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor weakness

Referenced by CAPEC · child of (3)

  • CAPEC-312 Active OS Fingerprinting attack pattern
  • CAPEC-313 Passive OS Fingerprinting attack pattern
  • CAPEC-541 Application Fingerprinting attack pattern

Referenced by CWE · attack pattern (1)

  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor weakness