CVE-2019-7393 json
A UI redress 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…
published 7y ago modified 4mo ago also EUVD-2019-16935
- cvss
- 4.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.3%
- EPSS 2.3% chance of exploitation in 30 days, percentile 83%
- public exploits
- 0
- none known
Summary
A UI redress 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 may allow a remote attacker to gain sensitive information in some cases.
Is CVE-2019-7393 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.28% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
Affected products
- CA Technologies, A Broadcom Company CA Strong Authentication
- CA Technologies, A Broadcom Company CA Risk Authentication
Classification
- Weakness
-
- CWE-1021 Improper Restriction of Rendered UI Layers or Frames
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-7393
- NVD CVE-2019-7393
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.