Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2019-7393: A UI redress vulnerability in the administrative user interface of CA Technologies CA Strong Authentication 9.

36
Routine
MEDIUM 4.3UPGRADEUPGRADE

CVE-2019-7393 is a medium-severity flaw (CVSS 4.3) affecting risk authentication, strong authentication. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score4.3 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance2.3% (top 17%)
CISA exploited listNo
WeaknessCWE-1021
Published2019-05-28
Last modified2026-06-17
Publisher (CNA): CA Technologies - A Broadcom Company · Vendor: ca

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

ca risk authentication UPGRADE
Affected: >= 8.0 and <= 8.2.1 · 3.1 · 9.0
Fixed in: newer than 8.2.1
Safe to downgrade to: a release before 3.1
1. Check installed version
apt-cache policy risk-authentication || rpm -q risk-authentication || risk-authentication --version
2. UPGRADE to newer than 8.2.1 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade risk-authentication
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade risk-authentication
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 3.1 (Debian / Ubuntu)
apt-cache madison risk-authentication sudo apt install risk-authentication=<VERSION_BEFORE_3.1> sudo apt-mark hold risk-authentication
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list risk-authentication sudo dnf downgrade risk-authentication-<VERSION_BEFORE_3.1> sudo dnf versionlock add risk-authentication
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
ca strong authentication UPGRADE
Affected: >= 8.0 and <= 8.2.1 · 7.1 · 9.0
Fixed in: newer than 8.2.1
Safe to downgrade to: a release before 7.1
1. Check installed version
apt-cache policy strong-authentication || rpm -q strong-authentication || strong-authentication --version
2. UPGRADE to newer than 8.2.1 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade strong-authentication
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade strong-authentication
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 7.1 (Debian / Ubuntu)
apt-cache madison strong-authentication sudo apt install strong-authentication=<VERSION_BEFORE_7.1> sudo apt-mark hold strong-authentication
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list strong-authentication sudo dnf downgrade strong-authentication-<VERSION_BEFORE_7.1> sudo dnf versionlock add strong-authentication
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-7393?

risk authentication: upgrade to newer than 8.2.1; strong authentication: upgrade to newer than 8.2.1. Exact commands for each OS are on this page.

Is CVE-2019-7393 being exploited?

CVE-2019-7393 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-7393 affect?

CVE-2019-7393 affects risk authentication, strong authentication. Severity is medium (CVSS 4.3). 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 s

How urgent is CVE-2019-7393?

Priority 36/100. No elevated risk signals yet.

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.