Skip to content
Fencer Intel
high 7.5

CVE-2019-13419 json

Search Guard versions before 23.1 had an issue that for aggregations clear text values of anonymised fields were leaked.

published 7y ago modified 4mo ago also EUVD-2019-4913

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 61%
public exploits
0
none known

Summary

Search Guard versions before 23.1 had an issue that for aggregations clear text values of anonymised fields were leaked.

Patch / fix

  • floragunn Search Guard 23.1

Is CVE-2019-13419 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-13419 updated cvss 5.3

search-guard: aggregations clear text values of anonymised fields were leaked

  • 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

0.93% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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-311 Missing Encryption of Sensitive Data
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel 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.