CVE-2019-7393
CVE-2019-7393 is a medium-severity vulnerability in Ca Risk Authentication with a CVSS 3.x base score of 4.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-1021.
Key facts
- Severity: Medium (CVSS 3.x base score 4.3)
- CVSS v2: 4.0
- EPSS exploit prediction: 2% (81st percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-1021
- Affected product: Ca Risk Authentication
- Published:
- Last modified:
Description
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.
Frequently asked questions
- What is CVE-2019-7393?
- 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.
- How severe is CVE-2019-7393?
- CVE-2019-7393 has a CVSS 3.x base score of 4.3, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
- Is CVE-2019-7393 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (81st percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2019-7393?
- CVE-2019-7393 primarily affects Ca Risk Authentication. In total, 6 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
- How do I fix CVE-2019-7393?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- When was CVE-2019-7393 published?
- CVE-2019-7393 was published on 2019-05-28 and last updated on 2026-06-17.
References
- http://packetstormsecurity.com/files/153089/CA-Risk-Strong-Authentication-Privilege-Escalation.html
- http://seclists.org/fulldisclosure/2019/May/43
- http://www.securityfocus.com/bid/108483
- https://seclists.org/bugtraq/2019/May/66
- https://support.ca.com/us/product-content/recommended-reading/security-notices/CA20190523-01--security-notice-for-ca-risk-authentication-and-ca-strong-authentication.html
Affected products (6)
- cpe:2.3:a:ca:risk_authentication:*:*:*:*:*:*:*:*
- cpe:2.3:a:ca:risk_authentication:3.1:*:*:*:*:*:*:*
- cpe:2.3:a:ca:risk_authentication:9.0:*:*:*:*:*:*:*
- cpe:2.3:a:ca:strong_authentication:*:*:*:*:*:*:*:*
- cpe:2.3:a:ca:strong_authentication:7.1:*:*:*:*:*:*:*
- cpe:2.3:a:ca:strong_authentication:9.0:*:*:*:*:*:*:*
More vulnerabilities in Ca Risk Authentication
- CVE-2019-7394 — High (CVSS 8.8): A privilege escalation vulnerability in the administrative user interface of CA Technologies CA Strong Authentication…
All CVEs affecting Ca Risk Authentication →
Other CWE-1021 vulnerabilities
- CVE-2021-43048 — Critical (CVSS 9.8): The Interior Server and Gateway Server components of TIBCO Software Inc.'s TIBCO PartnerExpress contain a vulnerability…
- CVE-2021-23274 — Critical (CVSS 9.8): The Config UI component of TIBCO Software Inc.'s TIBCO API Exchange Gateway and TIBCO API Exchange Gateway Distribution…
- CVE-2016-2496 — Critical (CVSS 9.8): The Framework UI permission-dialog implementation in Android 6.x before 2016-06-01 allows attackers to conduct…
- CVE-2021-21132 — Critical (CVSS 9.6): Inappropriate implementation in DevTools in Google Chrome prior to 88.0.4324.96 allowed a remote attacker to…
- CVE-2021-21111 — Critical (CVSS 9.6): Insufficient policy enforcement in WebUI in Google Chrome prior to 87.0.4280.141 allowed an attacker who convinced a…
- CVE-2024-10004 — Critical (CVSS 9.1): Opening an external link to an HTTP website when Firefox iOS was previously closed and had an HTTPS tab open could in…