CVE-2019-7394 json
A privilege escalation vulnerability in the administrative user interface of CA Technologies CA Strong Authentication 9.0.x, 8.2.x, 8.1.x,…
published 7y ago modified 4mo ago also EUVD-2019-16936
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.8%
- EPSS 2.8% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known
Summary
A privilege escalation vulnerability in the administrative user interface of CA Technologies CA Strong Authentication 9.0.x, 8.2.x, 8.1.x, 8.0.x, 7.1.x and CA Risk Authentication 9.0.x, 8.2.x, 8.1.x, 8.0.x, 3.1.x allows an authenticated attacker to gain additional privileges in some cases where an account has customized and limited privileges.
Is CVE-2019-7394 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 FencerExploit prediction
2.82% chance of exploitation in the next 30 days, higher than 86% 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:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
Affected products
- CA Technologies, A Broadcom Company CA Strong Authentication
- CA Technologies, A Broadcom Company CA Risk Authentication
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
References
-
support.ca.com
/us/product-content/recommended-reading/security-notices/CA20190523-01--security-notice-for-ca-risk-authentica
vendor-advisory
-
seclists.org
/bugtraq/2019/May/66
mailing-list, third-party-advisory
-
packetstormsecurity.com
/files/153089/CA-Risk-Strong-Authentication-Privilege-Escalation.html
third-party-advisory, vdb-entry
-
securityfocus.com
/bid/108483
vdb-entry, third-party-advisory
-
seclists.org
/fulldisclosure/2019/May/43
mailing-list, third-party-advisory
Sources
- CVE List CVE-2019-7394
- NVD CVE-2019-7394
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.