Vulnerability

Security Misconfiguration
detect, understand, remediate

Security misconfiguration is one of the most common vulnerability categories. Missing security headers, default credentials, verbose error messages, and unnecessary services expose applications to attack.

No credit card required. Free plan available forever.

Severity

Medium

CWE ID

CWE-16

OWASP Top 10

A05:2021 – Security Misconfiguration

CVSS 3.1 Score

6.5

What is security misconfiguration?

Security misconfiguration occurs when systems, frameworks, or applications are deployed with insecure default settings, incomplete configurations, open cloud storage, verbose error messages, or unnecessary features and services enabled. It is consistently the most common vulnerability category found during penetration tests and security assessments.

Unlike code-level vulnerabilities that require specific programming mistakes, misconfigurations arise from operational oversights: leaving default admin credentials, failing to disable directory listings, exposing stack traces to end users, or neglecting to apply security headers. These issues exist at every layer: web servers, application frameworks, databases, cloud services, and network devices.

The danger of security misconfiguration lies in its breadth and ease of exploitation. Automated scanners can discover these issues in seconds, and attackers routinely use them as initial footholds. A single misconfigured header or an exposed admin panel can be the entry point for a full compromise.

How it works

1

Scan for defaults

Attacker uses automated tools to scan for default configurations, open ports, exposed admin interfaces, and known default credentials.

2

Discover weaknesses

Finds missing security headers, verbose error messages, directory listings, exposed configuration files, or unnecessary services running.

3

Gather information

Uses disclosed information (stack traces, server versions, internal paths, and configuration details) to plan a targeted attack.

4

Exploit misconfiguration

Leverages the misconfiguration to gain unauthorised access, escalate privileges, or extract sensitive data from the system.

Common causes

Default configurations in production

Deploying applications and servers with out-of-the-box settings that prioritise ease of use over security, including default credentials and sample applications.

Unnecessary features enabled

Running services, ports, pages, accounts, or privileges that are not required, expanding the attack surface without providing value.

Missing security headers

Failing to configure HTTP security headers such as Content-Security-Policy, X-Frame-Options, Strict-Transport-Security, and X-Content-Type-Options.

Verbose errors and unpatched systems

Displaying detailed stack traces and error messages to users that reveal internal architecture, and running outdated software with known vulnerabilities.

How to detect it

Automated detection

  • SecPortal's 16-module external scanner checks security headers, SSL/TLS configuration, exposed paths, and information disclosure across your entire attack surface
  • Detects default pages, directory listings, exposed admin interfaces, and unnecessary services running on discovered ports
  • Continuous monitoring alerts on configuration drift, newly exposed services, and missing security headers after deployments

Manual testing

  • Review server and framework configurations against hardening benchmarks (CIS Benchmarks, vendor security guides)
  • Check for default pages, sample applications, and unnecessary HTTP methods (TRACE, OPTIONS) that should be disabled
  • Trigger application errors and verify that stack traces and internal details are not exposed to end users

How to fix it

Implement a hardening checklist per environment

Create and enforce security hardening standards for every environment (development, staging, production). Use CIS Benchmarks as a baseline.

Remove all defaults and unnecessary features

Change default credentials, remove sample applications, disable unused services and ports, and delete unnecessary accounts before deployment.

Configure security headers

Deploy Content-Security-Policy, Strict-Transport-Security, X-Frame-Options, X-Content-Type-Options, and Referrer-Policy headers on all responses.

Disable verbose error messages

Configure applications to return generic error pages to users while logging detailed error information server-side for debugging.

Automate configuration auditing

Use infrastructure-as-code and automated compliance scanning to detect and remediate configuration drift before it reaches production.

Compliance impact

Detect misconfigurations automatically

SecPortal's 16-module external scanner checks headers, SSL/TLS, exposed paths, and more. Start scanning for free.

No credit card required. Free plan available forever.