Skip to content
Fencer Intel
medium 4.6

CVE-2019-14849 json

A vulnerability was found in 3scale before version 2.6, did not set the HTTPOnly attribute on the user session cookie.

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

cvss
4.6
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 44%
public exploits
0
none known

Summary

A vulnerability was found in 3scale before version 2.6, did not set the HTTPOnly attribute on the user session cookie. An attacker could use this to conduct cross site scripting attacks and gain access to unauthorized information.

Patch / fix

  • redhat 3scale 2.6

Is CVE-2019-14849 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-14849 updated cvss 4.6

3scale: user session cookie does not set HTTPOnly

  • Red Hat 3scale API Management 2.6 3scale-amp26/zync 1.9-28, 3scale-amp26/backend 1.9-24, 3scale-amp26/toolbox latest, 3scale-amp26/operator latest, 3scale-amp26/3scale-operator latest, 3scale-amp26/apicast-gateway 1.15-9
    fixed: vendor fix RHSA-2019:2534

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.53% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.0 4.6 CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N
NVD 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
NVD 2.0 3.5 AV:N/AC:M/Au:S/C:N/I:P/A:N

Affected products

  • n/a 3scale

Classification

Weakness
  • CWE-201 Insertion of Sensitive Information Into Sent Data
  • CWE-79 Improper Neutralization of Input During Web Page Generation

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.