# Vulnerabilidades

## Identificación

### Common Vulnerabilities and Exposures (CVE) <a href="#identificacioncommon-vulnerabilities-and-exposures-cve" id="identificacioncommon-vulnerabilities-and-exposures-cve"></a>

* <https://cve.mitre.org/>

El CVE-ID ofrece una nomenclatura estándar para identificar las vulnerabilidades de forma inequívoca:

* El formato para CVE-ID es: CVE-YYYY-NNNN (YYYY indica el año y NNNN el número de vulnerabilidad). Desde enero de 2014 este identificador puede contener, si es necesario, más de cuatro dígitos.
* El formato para vulnerabilidades candidatas es: CAN-YYYY-NNNN (YYYY indica el año y NNNN el número de vulnerabilidad)

## Impacto

### Common Vulnerability Score System (CVSS)

* <https://www.first.org/cvss/>

## Clasificación

### Common Weakness Enumeration (CWE)

* <https://cwe.mitre.org/>

### OWASP Web Top 10

* <https://owasp.org/www-project-top-ten/>

### OWASP Mobile Top 10

* <https://owasp.org/www-project-mobile-top-10/>

### OWASP API Security Top 10

* <https://owasp.org/www-project-api-security/>

### Common Attack Pattern Enumeration and Classification (CAPEC)

* <https://capec.mitre.org/>

### The WASC Threat Classification

* <http://projects.webappsec.org/Threat-Classification>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://pentesting.mrw0l05zyn.cl/general/vulnerabilidades.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.