Notes - MCS
Analysis and Exploration of Vulnerabilities
Notes - MCS
Analysis and Exploration of Vulnerabilities
  • Analysis and Exploration of Vulnerabilities
  • Vulnerabilities
    • Vulnerabilities
      • CIA Triad
      • Vulnerability Sources
    • Vulnerability Tracking
    • Vulnerability Disclosure
  • Vulnerability Assessment of Networked Systems
    • Vulnerability Research
    • Vulnerability Assessment
    • Penetration Test
      • Scope
    • Types of Assessments
    • Vulnerability Management Life Cycle
  • Enumeration and Information Leakage
    • Network access
    • Information leakage
    • Errors
    • Web Sources and Support Files
    • Cookies
    • Ports
    • Banners
    • OS Fingerprinting
  • Injection
    • CWE-74
    • How it works
    • Common Pitfalls
    • CWE-89 SQL Injection
    • Using SQL
    • Things to consider
    • The NULL plate
    • SQLi types
    • SQL Injection - Avoiding
    • CWE-78 OS Command Injection
    • Command Override
    • Argument Exploitation
    • GTFOBins and LOLBAS
    • Environmental Variables
    • Parameter Expansion
    • Code Injection - CWE-94
    • Avoiding OS Injection
  • Broken Authentication
    • OWASP A2
    • HTTP Basics
    • HTTP Communication
    • Authentication
    • Authentication Flow State
    • Referer Header
    • SESSION ID
    • Cookies (RFC 6265)
    • JWT - JSON Web Tokens
  • XSS Cross Site Scripting
    • Prevalence and Detectability
    • Reflected XSS
    • Stored XSS
    • DOM XSS
    • Cross Site Request Forgery
    • Avoiding XSS
    • Same Origin Policy
  • Concurrency
    • Concurrency
    • CWE-361 - 7PK - Time and State
    • Basic Time Related CWEs
      • CWE-362 – Race Condition
    • Serializability
    • Database ACID characteristic
    • State Related CWEs
    • Basic Side Effects Related CWEs (Covert Channel)
    • Covert Timing Channel
    • Meltdown Type
  • Buffers
    • Buffer Overflow
    • Popularity decline
    • Potentially Vulnerable Software
    • Dominant prevalence
    • Vulnerabilities in languages (mostly C/C++)
    • Why? Memory Structure 101
    • CWE-120 Classic Overflow
      • Practical Examples
    • Stack Based Vulnerabilities
    • Stack Smashing
    • Countermeasures
    • ROP
Powered by GitBook
On this page
  • Information leakage
  • Mitigation
  1. Enumeration and Information Leakage

Ports

The network stack behaves differently whether the ports are open or closed

  • TCP: replies with a TCP SYN, ACK (if open), or TCP RST (if closed).

  • UDP: replies with a Higher Layer packet (if open), or an ICMP Port unreachable (if closed).

  • ICMP: replies with ICMP Reply (or other).

  • Firewalls also affect replies by altering or filtering packets.

Services typically operate on well-known ports.

  • All ports below 1024 are reserved for popular services.

  • Many ports above 1024 are also reserved.

Impact: Allows knowing which services/hosts are available.

Information leakage

Port scan: try to initiate a connection to a specific port.

  • May effectively initiate the connection or may simply start initiating it.

    • Full Connection: Doing the TCP Three-Way Handshake.

    • Half Connection: Only sending the first TCP SYN.

  • A reply may indicate the existence/absence of a service.

    • Existence if the connection is successful.

    • Absence if an error is received.

  • A non-reply may indicate the existence of a firewall.

Mitigation

Mitigation is limited as it exploits an inherent behavior.

  • The network port state will affect the replies.

Firewalls should observe connect attempts and limit them on the detection of enumeration.

  • Number of connections from a given host.

  • Different ports are being accessed.

  • Session duration.

  • Rate of packets.

  • Specific fingerprints.

Last updated 1 year ago