Skip to content
Fencer Intel
medium 5.9

CVE-2019-13420 json

Search Guard versions before 21.0 had an timing side channel issue when using the internal user database.

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

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

Summary

Search Guard versions before 21.0 had an timing side channel issue when using the internal user database.

Patch / fix

  • floragunn Search Guard 21.0

Is CVE-2019-13420 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-13420 updated cvss 5.9

search-guard: timing side channel issue when using the internal user database

  • Red Hat OpenShift Container Platform 3.9 search-guard-2, openshift-elasticsearch-plugin Red Hat OpenShift Container Platform 3.10 openshift-elasticsearch-plugin 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 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.19% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N

Affected products

  • floragunn Search Guard

Classification

Weakness
  • CWE-208 Observable Timing Discrepancy
  • CWE-203 Observable Discrepancy

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.