Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
CWE-548 Variante Borrador
Exposure of Information Through Directory Listing
This vulnerability occurs when a web server is misconfigured to display a full list of files within a directory instead of serving a default web page, unintentionally exposing sensitive resources to…
Definición
What is CWE-548?
This vulnerability occurs when a web server is misconfigured to display a full list of files within a directory instead of serving a default web page, unintentionally exposing sensitive resources to anyone who visits the URL.
Directory listings happen when a web server (like Apache, Nginx, or IIS) can't find a default index file (e.g., index.html) and its configuration allows it to show the folder's contents. This acts as a roadmap for attackers, revealing backup files, configuration scripts, temporary uploads, or administrative interfaces that were never meant to be public. A simple manual check or a DAST scan can easily uncover this issue.
Prevention involves configuring your server to disable directory listings and always ensuring a default index page exists. For developers, this means checking server configuration files for directives like 'Options -Indexes' in Apache or 'autoindex off' in Nginx. Managing this at scale across hundreds of services is difficult; an ASPM like Plexicus can help you continuously track and automatically flag these misconfigurations across your entire application portfolio.
Impacto en el mundo real
Real-world CVEs caused by CWE-548
Todavía no hay CVEs públicos enlazados a esta CWE en el catálogo de MITRE.
Cómo lo explotan los atacantes
Ruta del atacante paso a paso
- 1
Identifica una ruta de código que maneje entrada no confiable sin validación.
- 2
Crea un payload que ejercite el comportamiento inseguro — inyección, traversal, overflow o abuso de lógica.
- 3
Envía el payload a través de una solicitud normal y observa la reacción de la aplicación.
- 4
Itera hasta que la respuesta filtre datos, ejecute código del atacante o escale privilegios.
Ejemplo de código vulnerable
Vulnerable pseudo
MITRE no ha publicado un ejemplo de código para esta CWE. El patrón siguiente es ilustrativo — consulta Recursos para referencias canónicas.
// Example pattern — see MITRE for the canonical references.
function handleRequest(input) {
// Untrusted input flows directly into the sensitive sink.
return executeUnsafe(input);
} Ejemplo de código seguro
Secure pseudo
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
const safe = validateAndEscape(input);
return executeWithGuards(safe);
} What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Lista de prevención
How to prevent CWE-548
- Architecture and Design / System Configuration Recommendations include restricting access to important directories or files by adopting a need to know requirement for both the document and server root, and turning off features such as Automatic Directory Listings that could expose private files and provide information that could be utilized by an attacker when formulating or conducting an attack.
Señales de detección
How to detect CWE-548
CWE-548
Don't catalog this weakness. Prove it's reachable.
Plexicus turns CWE catalogs into evidence: every CWE-pattern is matched against your real code graph, reach is proven on a sandbox clone, and verified findings ship as reviewed PRs.
Preguntas frecuentes ¿Qué es CWE-548?
¿Qué gravedad tiene CWE-548?
¿Qué lenguajes o plataformas se ven afectados por CWE-548?
¿Cómo puedo prevenir CWE-548?
¿Cómo detecta y corrige Plexicus CWE-548?
¿Dónde puedo aprender más sobre CWE-548?
Frequently asked questions
¿Qué es CWE-548?
This vulnerability occurs when a web server is misconfigured to display a full list of files within a directory instead of serving a default web page, unintentionally exposing sensitive resources to anyone who visits the URL.
¿Qué gravedad tiene CWE-548?
MITRE no ha publicado una calificación de probabilidad de explotación para esta debilidad. Trátala como de impacto medio hasta que tu modelo de amenazas demuestre lo contrario.
¿Qué lenguajes o plataformas se ven afectados por CWE-548?
MITRE no ha especificado plataformas afectadas para esta CWE — puede aplicar a la mayoría de los stacks de aplicaciones.
¿Cómo puedo prevenir CWE-548?
Recommendations include restricting access to important directories or files by adopting a need to know requirement for both the document and server root, and turning off features such as Automatic Directory Listings that could expose private files and provide information that could be utilized by an attacker when formulating or conducting an attack.
¿Cómo detecta y corrige Plexicus CWE-548?
El motor SAST de Plexicus detecta la firma de flujo de datos para CWE-548 en cada commit. Cuando hay coincidencia, nuestro agente Codex Remedium abre un PR de corrección con el código corregido, las pruebas y un resumen de una línea para el revisor.
¿Dónde puedo aprender más sobre CWE-548?
MITRE publica la definición canónica en https://cwe.mitre.org/data/definitions/548.html. También puedes consultar la documentación de OWASP y NIST para guías relacionadas.
Debilidades relacionadas
Weaknesses related to CWE-548
CWE-497 Padre
Exposure of Sensitive System Information to an Unauthorized Control Sphere
This vulnerability occurs when an application unintentionally reveals sensitive details about its underlying system, such as file paths,…
CWE-214 Hermano
Invocation of Process Using Visible Sensitive Information
This vulnerability occurs when a process is started with sensitive data, such as passwords or API keys, passed directly in its…
¿Listo para validar lo que importa?
Listo para validar lo que importa.
Plexicus es Proof-Driven AppSec: hallazgos validados, comprensión contextual y remediación revisada — anclada en evidencia, acotada contigo.