Skip to content
Fencer Vulns
medium 5.3

CVE-2019-13417 json

Search Guard versions before 24.0 had an issue that field caps and mapping API leak field names (but not values) for fields which are not a…

published 2019-08-12 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-4911

cvss
5.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 65%
public exploits
0
none known

Summary

Search Guard versions before 24.0 had an issue that field caps and mapping API leak field names (but not values) for fields which are not allowed for the user when field level security (FLS) is activated.

Patch / fix

  • floragunn Search Guard 24.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-13417 updated cvss 4.3

search-guard: information disclosure in field level security (FLS)

  • Red Hat OpenShift Container Platform 3.11 openshift3/ose-logging-elasticsearch5 Red Hat OpenShift Container Platform 4 openshift4/ose-logging-elasticsearch5
    affected: no fix available “Fix deferred”
  • Red Hat OpenShift Container Platform 3.9 search-guard-2, openshift-elasticsearch-plugin Red Hat OpenShift Container Platform 3.10 openshift-elasticsearch-plugin
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.10% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N

Affected products

  • floragunn Search Guard

Classification

Weakness
  • CWE-863 Incorrect Authorization
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.