CVE-2019-7394
CVE-2019-7394 Vulnerability Analysis & Exploit Intelligence
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.
Published Updated Sources: cvelistV5, ca
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
3%
chance of exploitation in 30 days
CVSS base
Unscored
no source published a base score
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (2)
Weakness & attack patterns
- CWE-269
Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.
- T1548Abuse Elevation Control Mechanism
References
5 on the record
- seclists.org/bugtraq/2019/May/66
mailing-list, x_refsource_BUGTRAQ
- packetstormsecurity.com/files/153089/CA-Risk-Strong-Authentication-Privilege-Escalation.html
x_refsource_MISC
- www.securityfocus.com/bid/108483
vdb-entry, x_refsource_BID
- support.ca.com/us/product-content/recommended-reading/security-notices/CA20190523-01--security-notice-for-ca-risk-authentication-and-ca-strong-authentication.html
x_refsource_CONFIRM
- seclists.org/fulldisclosure/2019/May/43
mailing-list, x_refsource_FULLDISC
Elsewhere on this site
- ca technologies a broadcomevery CVE for this vendor
- CWE-269other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.