Cybersecurity Notes intermediate

Module 05 — Vulnerability Analysis

Understanding vulnerabilities, risk assessment, validation, prioritization, and remediation — CEH Module 05 notes with severity levels, CVE/CVSS/CWE/CAPEC and tooling.

Updated Aug 4, 2026 7 min read 5 views
#CEH#Vulnerability Analysis#CVSS#CVE#CWE#CAPEC#Nessus#OpenVAS
Back to category

Understanding vulnerabilities, risk assessment, validation, prioritization, and remediation.

Info

Module 05 — Vulnerability Analysis. Everything below is exam-ready: definitions, comparison tables, the analysis workflow, vulnerability types, severity levels, the CVE/CVSS/CWE/CAPEC standards and the tooling reference.

1. What is Vulnerability Analysis?

Definition

Vulnerability Analysis is the process of identifying, analyzing, validating, and prioritizing security weaknesses (vulnerabilities) in systems, networks, applications, or infrastructure before they can be exploited.

The goal is to determine:

  • What vulnerabilities exist?
  • How severe are they?
  • Can they be exploited?
  • What impact would exploitation have?
  • How should they be remediated?

Important

Unlike simple scanning, vulnerability analysis focuses on understanding risk, not just discovering open ports or services.

Simple Definition

Note

Vulnerability Analysis is the process of identifying security weaknesses, assessing their risk, validating their existence, and recommending remediation before attackers can exploit them.

Example

Suppose Nmap finds:

terminal
80/tcp open http Apache 2.4.49

Scanning only tells us:

terminal
Apache is running.

Vulnerability Analysis asks:

  • Is Apache 2.4.49 vulnerable?
  • What CVEs affect it?
  • Can attackers exploit it?
  • Is a patch available?
  • How severe is it?
  • What should be fixed first?

This is Vulnerability Analysis.

2. Vulnerability Analysis vs Exploitation

Vulnerability AnalysisExploitation
Finds vulnerabilitiesUses vulnerabilities
Passive/assessment-focusedActive attack phase
Identifies riskDemonstrates impact
Produces remediation adviceAttempts to gain access
Usually non-destructiveMay alter system state
Example: Nessus scanExample: Metasploit module

Example

Vulnerability Analysis

You discover:

terminal
Apache 2.4.49

Research shows:

terminal
CVE-2021-41773

Severity:

terminal
Critical

Recommendation:

terminal
Update Apache immediately.

Exploitation

A tester later uses an exploit targeting CVE-2021-41773 to demonstrate the impact in an authorized environment.

3. Why Do We Perform Vulnerability Analysis?

Organizations usually have thousands of devices.

Every device may contain multiple vulnerabilities.

Without analysis:

  • Everything looks equally important.
  • Security teams don't know what to fix first.
  • Resources are wasted.

Tip

Vulnerability Analysis helps prioritize remediation.

Why Analyze Vulnerabilities?

Because we need to understand:

  • Which systems are vulnerable?
  • Which vulnerabilities are exploitable?
  • Which pose the greatest business risk?
  • Which require immediate remediation?

Why Don't We Exploit Immediately?

Finding a vulnerability does not necessarily mean it should be exploited.

Reasons include:

1. Avoid System Damage

Warning

Some exploits can crash services or destabilize systems.

Example:

terminal
Production Database

Crashing it could interrupt business operations.

2. Verify the Finding

Scanners sometimes report issues that are not actually exploitable.

Example:

terminal
Scanner reports SQL Injection
Manual testing finds none.

That is a false positive.

3. Maintain Stability

Organizations often prefer:

terminal
Identify → Validate → Patch

instead of

terminal
Identify → Exploit

4. Respect Scope and Authorization

Caution

Many engagements permit identification and validation but restrict exploitation unless explicitly authorized.

4. Benefits of Vulnerability Validation

Validation confirms whether a reported issue is genuine.

Benefits:

  • Removes false positives
  • Reduces unnecessary work
  • Improves report accuracy
  • Prevents incorrect remediation
  • Builds confidence in findings

5. Risk Reduction

The purpose is not simply to find vulnerabilities.

The goal is to reduce organizational risk.

Example:

terminal
Critical Vulnerability
        │
        ▼
      Patch
        │
        ▼
  Reduced Risk

6. Prioritizing Vulnerabilities

Organizations cannot always fix everything immediately.

Therefore vulnerabilities are prioritized.

Typical order:

terminal
Critical
   │
   ▼
  High
   │
   ▼
 Medium
   │
   ▼
  Low
   │
   ▼
Informational

Priority depends on factors such as:

  • Severity
  • Ease of exploitation
  • Business impact
  • Internet exposure
  • Availability of patches

7. False Positives

Definition

Note

A False Positive is a vulnerability reported by a scanner that does not actually exist after verification.

Example:

Scanner:

terminal
SQL Injection Found

Manual testing:

terminal
No SQL Injection

Result:

terminal
False Positive

Why Do False Positives Occur?

  • Banner version detection
  • Incorrect signatures
  • Configuration differences
  • Scanner limitations
  • Environmental factors

8. Vulnerability Analysis Workflow

terminal
Reconnaissance
        │
        ▼
Scanning
        │
        ▼
Enumeration
        │
        ▼
Vulnerability Analysis
        │
        ▼
Validation
        │
        ▼
Risk Assessment
        │
        ▼
Exploitation (if authorized)
        │
        ▼
Reporting
        │
        ▼
Remediation

9. Types of Vulnerabilities

1. Network Vulnerabilities

Weaknesses affecting network infrastructure.

Examples:

  • Open ports
  • SMBv1 enabled
  • Weak TLS configuration
  • Insecure network services
  • Firewall misconfigurations

2. Web Application Vulnerabilities

Weaknesses in websites or APIs.

Examples:

  • SQL Injection
  • Cross-Site Scripting (XSS)
  • Cross-Site Request Forgery (CSRF)
  • File Inclusion
  • Command Injection
  • Directory Traversal

3. Operating System Vulnerabilities

Weaknesses in Windows, Linux, or other operating systems.

Examples:

  • Missing security patches
  • Local privilege escalation flaws
  • Weak file permissions
  • Outdated kernel versions

4. Database Vulnerabilities

Weaknesses affecting databases.

Examples:

  • Default credentials
  • Weak passwords
  • Excessive privileges
  • SQL Injection exposure
  • Unencrypted data

5. Wireless Vulnerabilities

Weaknesses in wireless networks.

Examples:

  • Weak Wi-Fi passwords
  • WEP encryption
  • Rogue access points
  • Evil Twin attacks
  • Weak WPA configuration

6. Configuration Weaknesses

Security issues caused by poor configuration.

Examples:

  • Default credentials
  • Default settings
  • Open directory listing
  • Public cloud storage
  • Debug mode enabled

7. Authentication Weaknesses

Weaknesses in user authentication.

Examples:

  • Weak passwords
  • Password reuse
  • No MFA
  • Predictable passwords
  • Default accounts

8. Authorization Issues

Users can access resources they should not.

Examples:

  • Insecure Direct Object References (IDOR)
  • Broken Access Control
  • Privilege escalation
  • Horizontal privilege escalation
  • Vertical privilege escalation

9. Business Logic Issues

Application behavior can be abused without exploiting a software bug.

Examples:

  • Applying a coupon multiple times
  • Bypassing payment steps
  • Purchasing items at incorrect prices
  • Abuse of referral systems

10. Cryptographic Weaknesses

Problems related to encryption and key management.

Examples:

  • Weak hashing algorithms (MD5, SHA-1)
  • Weak SSL/TLS configuration
  • Hardcoded encryption keys
  • Poor random number generation

10. Vulnerability Severity Levels

Critical

  • Immediate exploitation is likely.
  • Major impact on confidentiality, integrity, or availability.
  • Requires urgent remediation.

Example:

terminal
Remote Code Execution

High

  • Significant risk.
  • Exploitable with some conditions.
  • Should be remediated quickly.

Example:

terminal
SQL Injection

Medium

  • Moderate impact.
  • May require user interaction or specific conditions.

Example:

terminal
Directory Listing Enabled

Low

  • Limited security impact.
  • Usually combined with other issues.

Example:

terminal
Server Version Disclosure

Informational

  • Not a vulnerability by itself.
  • Useful for security awareness.

Example:

terminal
Server Banner Disclosure

11. CVE (Common Vulnerabilities and Exposures)

Note

A CVE is a unique identifier assigned to a publicly known security vulnerability.

Example:

terminal
CVE-2021-41773

A CVE identifies which vulnerability is being discussed.

12. CVSS (Common Vulnerability Scoring System)

CVSS provides a numerical severity score.

Typical ranges:

ScoreSeverity
0.0None
0.1–3.9Low
4.0–6.9Medium
7.0–8.9High
9.0–10.0Critical

CVSS answers:

Tip

"How severe is this vulnerability?"

13. CWE (Common Weakness Enumeration)

A CWE describes the underlying software weakness that leads to vulnerabilities.

Examples:

  • CWE-79 → Cross-Site Scripting
  • CWE-89 → SQL Injection
  • CWE-287 → Improper Authentication

Think of CWE as the category of weakness.

14. CAPEC (Common Attack Pattern Enumeration and Classification)

CAPEC documents common attack techniques used by attackers.

Example:

  • SQL Injection attack pattern
  • Cross-Site Scripting attack pattern
  • Phishing attack pattern

CAPEC answers:

Tip

"How might an attacker exploit this type of weakness?"

15. Relationship Between CVE, CVSS, CWE, and CAPEC

StandardPurpose
CVEIdentifies a specific publicly known vulnerability.
CVSSScores the severity of that vulnerability.
CWEDescribes the underlying software weakness.
CAPECDescribes common attack techniques used to exploit weaknesses.

16. Vulnerability Analysis Tools

1. Nessus Essentials

Purpose

  • Industry-standard vulnerability scanner
  • Detects CVEs, missing patches, weak configurations, and security misconfigurations
  • Generates detailed reports

Why use it?

  • Fast
  • Accurate
  • Excellent reporting
  • Enterprise standard

Platform: Windows, Linux, macOS

Download: Nessus Essentials

2. OpenVAS (Greenbone)

Purpose

  • Free, open-source vulnerability scanner
  • Detects known vulnerabilities and configuration issues

Why use it?

  • Completely free
  • Large vulnerability database
  • Good alternative to Nessus

Platform: Linux, Docker

Download: Greenbone Community Edition

3. Nmap NSE

Purpose

  • Detects known vulnerabilities using Nmap scripts
  • Performs service-specific security checks

Why use it?

  • Fast
  • Lightweight
  • Ideal for quick vulnerability checks

Platform: Windows, Linux, macOS

Download: Nmap Downloads

4. Nikto

Purpose

  • Web server vulnerability scanner

Finds

  • Outdated software
  • Dangerous files
  • Misconfigurations
  • Default pages

Download: Nikto GitHub

5. Burp Suite Community

Purpose

  • Manual web application security testing

Finds

  • SQL Injection
  • XSS
  • IDOR
  • Authentication flaws

Download: Burp Suite Community Edition

6. OWASP ZAP

Purpose

  • Automated web application vulnerability scanner

Finds

  • XSS
  • SQL Injection
  • Missing security headers
  • Weak cookies

Download: OWASP ZAP

7. WPScan

Purpose

  • WordPress vulnerability scanner

Finds

  • Vulnerable plugins
  • Vulnerable themes
  • Outdated WordPress
  • User enumeration

Download: WPScan Official Site