Kibana /api/status Exposed
kibana-api-status-exposed is a medium severity check in the
monitoring category, written in yaml.
Its source is templates/monitoring/kibana/kibana-api-status-exposed.yaml in
cert-x-gen-templates.
What it checks
Section titled “What it checks”Detects Kibana instances that expose the /api/status endpoint without authentication. Exposed status endpoints can leak version and cluster information useful for attackers.
Header
Section titled “Header”| Field | Value |
|---|---|
| Id | kibana-api-status-exposed |
| Severity | medium |
| Language | yaml |
| Category | monitoring |
| Author | CERT-X-GEN Security Team |
| Template version | 1.0.0 |
| Confidence | 85 |
| CVSS | 5.3 |
| Weakness | CWE-200 |
| Tags | kibana, elastic, monitoring, information-disclosure, exposure |
| Target kind | not recorded |
| Oracle | not recorded |
The file declares http, remediation as well. Those are not tabled above; read the
source for what they carry.
References
Section titled “References”Declared in the header. cxg parses @references and then discards it, and
nothing at scan time reads it, so this is the only place the links a
template cites are surfaced.
- https://www.elastic.co/guide/en/kibana/current/api.html
- https://cwe.mitre.org/data/definitions/200.html
Run it
Section titled “Run it”To see what the copy on your machine says about itself, and to confirm it is installed at all:
cxg template info kibana-api-status-exposedThe id it prints is the one to pass anywhere a template is selected. See
cxg template for the rest of
the subcommand, Scan a target for running
a scan, and
A match is not a finding for how
to read what comes back.
Related
Section titled “Related”- Template catalog is the whole corpus.
- monitoring is the rest of this category.
- Templates by weakness class groups checks by the defect they look for.
- Contribute a template is the route from a check you needed and could not find to a merged one.