CVE-2019-14836 json
A vulnerability was found that the 3scale dev portal does not employ mechanisms for protection against login CSRF.
published 5y ago modified 4mo ago also EUVD-2019-5962
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 47%
- public exploits
- 0
- none known
Summary
A vulnerability was found that the 3scale dev portal does not employ mechanisms for protection against login CSRF. An attacker could use this flaw to access unauthorized information or conduct further attacks.
Is CVE-2019-14836 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 FencerVendor 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-14836 updated cvss 5.4
3scale: dev portal missing protection against login CSRF
-
Red Hat 3Scale AMP 2.10 3scale-amp2/3scale-rhel7-operator 1.13.0-17, 3scale-amp2/apicast-rhel7-operator 1.13.0-4, 3scale-amp2/3scale-rhel7-operator-metadata 3scale2.10.0, 3scale-amp2/apicast-rhel7-operator-metadata 3scale2.10.0fixed: vendor fix RHSA-2021:1129
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.58% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected products
- n/a Red Hat 3scale API Management
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
bugzilla.redhat.com
/show_bug.cgi?id=1847605
vendor-advisory
Sources
- CVE List CVE-2019-14836
- NVD CVE-2019-14836
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.