Home > CAPEC List > CAPEC-325: TCP Congestion Control Flag (ECN) Probe (Version 2.10)  

CAPEC-325: TCP Congestion Control Flag (ECN) Probe

 
TCP Congestion Control Flag (ECN) Probe
Definition in a New Window Definition in a New Window
Attack Pattern ID: 325
Abstraction: Detailed
Status: Stable
Completeness: Complete
Presentation Filter:
+ Summary

This OS fingerprinting probe checks to see if the remote host supports explicit congestion notification (ECN) messaging. ECN messaging was designed to allow routers to notify a remote host when signal congestion problems are occurring. Explicit Congestion Notification messaging is defined by RFC 3168. Different operating systems and versions may or may not implement ECN notifications, or may respond uniquely to particular ECN flag types.

+ Target Attack Surface

Target Attack Surface Description

Targeted OSI Layers: Network Layer

Target Attack Surface Localities

Server-side

Target Attack Surface Types: Host

Target Functional Services

Target Functional Service 1: None
Protocol 1: IPProtocol 2: TCP
Protocol Header 1: IP Header
Protocol RFCProtocol Field NameProtocol Field DescriptionProtocol Operation Code
RFC 3168
Explicit Congestion Notification (ECN) field. Bits 6 and 7 in the IPv4 TOS octet are designated as the ECN field.
The not-ECT codepoint '00' indicates a packet that is not using ECN.
00
Protocol Header 2: IP Header
Protocol RFCProtocol Field NameProtocol Field DescriptionProtocol Operation Code
RFC 3168
Explicit Congestion Notification (ECN) field. Bits 6 and 7 in the IPv4 TOS octet are designated as the ECN field.
The ECT(1) bit. Binary flag '01' indicates a packet is using ECN(1) channel.
01
Protocol Header 3: IP Header
Protocol RFCProtocol Field NameProtocol Field DescriptionProtocol Operation Code
RFC 3168
Explicit Congestion Notification (ECN) field. Bits 6 and 7 in the IPv4 TOS octet are designated as the ECN field.
The ECT(0) bit. Binary flag '10' indicates a packet is using ECT(0) channel.
10
Protocol Header 4: IP Header
Protocol RFCProtocol Field NameProtocol Field DescriptionProtocol Operation Code
RFC 3168
Explicit Congestion Notification (ECN) field. Bits 6 and 7 in the IPv4 TOS octet are designated as the ECN field.
The CE codepoint '11' is set by a router to indicate congestion to the end nodes.
11
Related Protocol: Internet Protocol
Relationship Type
Uses Protocol
Protocol Header 5: TCP Header
Protocol RFCProtocol Field NameProtocol Field DescriptionProtocol Operation Code
RFC 3168
Reserved Field
ECN-Echo flag. The ECN-Echo flag is assigned to Bit 9 in the Reserved field of the TCP header.
ECE
Protocol Header 6: TCP Header
Protocol RFCProtocol Field NameProtocol Field DescriptionProtocol Operation Code
RFC 3168
Reserved Field
CWR Flag. The CWR flag is assigned to Bit 8 in the Reserved field of the TCP header.
CWR
Related Protocol: Transmission Control Protocol
Relationship Type
Uses Protocol
+ Attack Prerequisites
  • The ability to monitor and interact with network communications.

    Access to at least one host, and the privileges to interface with the network interface card.

+ Typical Severity

Low

+ Typical Likelihood of Exploit

Likelihood: Medium

+ Resources Required

A tool capable of sending and receiving packets from a remote system.

+ Attack Motivation-Consequences
ScopeTechnical ImpactNote
Confidentiality
Read application data
Confidentiality
Access_Control
Authorization
Bypass protection mechanism
Hide activities
+ References
[R.325.1] [REF-20] Stuart McClure, Joel Scambray and George Kurtz. "Hacking Exposed: Network Security Secrets & Solutions". Chapter 2: Scanning, pg. 56. 6th Edition. McGraw Hill. 2009.
[R.325.2] [REF-21] Defense Advanced Research Projects Agency Information Processing Techniques Office and Information Sciences Institute University of Southern California. "RFC793 - Transmission Control Protocol". Defense Advanced Research Projects Agency (DARPA). September 1981. <http://www.faqs.org/rfcs/rfc793.html>.
[R.325.3] [REF-22] Gordon "Fyodor" Lyon. "Nmap Network Scanning: The Official Nmap Project Guide to Network Discovery and Security Scanning". Chapter 8. Remote OS Detection. 3rd "Zero Day" Edition,. Insecure.com LLC. 2008.
+ Content History
Submissions
SubmitterOrganizationDateSource
CAPEC Content TeamThe MITRE Corporation2014-06-23Internal_CAPEC_Team
Modifications
ModifierOrganizationDateCommentsSource
CAPEC Content TeamThe MITRE Corporation2017-05-01Updated Attack_Motivation-Consequences, Attack_Prerequisites, Related_Attack_Patterns, Resources_Required, Typical_Likelihood_of_ExploitInternal
More information is available — Please select a different filter.
Page Last Updated or Reviewed: May 01, 2017