Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2017-2110: The Access CX App for Android prior to 2.0.0.1 and for iOS prior to 2.0.2 does not verify X.509 certificates f

38
Routine
MEDIUM 5.9REMOTEUPGRADEUPGRADE

CVE-2017-2110 is a medium-severity flaw (CVSS 5.9) affecting access cx, access cx. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Access CX App for Android prior to 2.0.0.1 and for iOS prior to 2.0.2 does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate.

Why this priority

  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score5.9 (Medium)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededNone
User interactionNone
EPSS exploit chance0.6% (top 49%)
CISA exploited listNo
WeaknessCWE-295
Published2017-04-28
Last modified2026-06-17
Publisher (CNA): JPCERT/CC · Vendor: nissan securities

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

nissan securities access cx UPGRADE
Affected: <= 2.0.0.0
Fixed in: newer than 2.0.0.0
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy access-cx || rpm -q access-cx || access-cx --version
2. UPGRADE to newer than 2.0.0.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade access-cx
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade access-cx
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
nissan securities access cx UPGRADE
Affected: <= 2.0.1
Fixed in: newer than 2.0.1
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy access-cx || rpm -q access-cx || access-cx --version
2. UPGRADE to newer than 2.0.1 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade access-cx
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade access-cx
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
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-2017-2110?

access cx: upgrade to newer than 2.0.0.0; access cx: upgrade to newer than 2.0.1. Exact commands for each OS are on this page.

Is CVE-2017-2110 being exploited?

CVE-2017-2110 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-2017-2110 affect?

CVE-2017-2110 affects access cx, access cx. Severity is medium (CVSS 5.9). The Access CX App for Android prior to 2.0.0.1 and for iOS prior to 2.0.2 does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certific

How urgent is CVE-2017-2110?

Priority 38/100. Remotely exploitable, no login, no user action

Software pages

Android vulnerabilities · iOS vulnerabilities

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.