Skip to content
Fencer Intel
medium 6.5

CVE-2019-3996 json

ELOG 3.1.4-57bea22 and below can be used as an HTTP GET request proxy when unauthenticated remote attackers send crafted HTTP POST requests.

published 6y ago modified 4mo ago also EUVD-2019-13603

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

Summary

ELOG 3.1.4-57bea22 and below can be used as an HTTP GET request proxy when unauthenticated remote attackers send crafted HTTP POST requests.

Patch / fix

Is CVE-2019-3996 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-3996 updated cvss 6.5

elog: unauthenticated remote users can proxy HTTP GET requests via crafted POST requests

  • Red Hat All currently supported Red Hat products
    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

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

Exploits and checks

  • tenable.com https://www.tenable.com/security/research/tra-2019-53 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected products

  • n/a ELOG

Classification

Weakness
  • CWE-441 Unintended Proxy or Intermediary
  • CWE-610 Externally Controlled Reference to a Resource in Another Sphere

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.