Skip to content
Fencer Intel
medium 5.9

CVE-2019-11323 json

HAProxy before 1.9.7 mishandles a reload with rotated keys, which triggers use of uninitialized, and very predictable, HMAC keys.

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

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

Summary

HAProxy before 1.9.7 mishandles a reload with rotated keys, which triggers use of uninitialized, and very predictable, HMAC keys. This is related to an include/types/ssl_sock.h error.

Patch / fix

  • haproxy haproxy 1.9.7

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

haproxy: weak HMAC keys used to TLS session resumption after reload with rotated keys

  • Red Hat Enterprise Linux 6 haproxy Red Hat Enterprise Linux 7 haproxy Red Hat Enterprise Linux 8 haproxy Red Hat OpenShift Container Platform 3.7 haproxy18 Red Hat OpenShift Container Platform 3.9 haproxy, haproxy18 Red Hat OpenShift Container Platform 3.10 haproxy, haproxy18
    +4 more products
    Red Hat OpenShift Container Platform 3.11 haproxy, haproxy18 Red Hat OpenShift Container Platform 4 haproxy, haproxy18, haproxy20, haproxy22, haproxy26, haproxy28 Red Hat OpenShift Enterprise 3 haproxy, haproxy18 Red Hat Software Collections rh-haproxy18-haproxy, rh-haproxy18-haproxy-syspaths
    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.25% chance of exploitation in the next 30 days, higher than 69% 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

Classification

Weakness
  • CWE-327 Use of a Broken or Risky Cryptographic Algorithm
  • CWE-908 Use of Uninitialized Resource

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.