CVE-2014-5799: The smart.card (aka nh.smart.card) application 3.2 for Android does not verify X.509 certificates from SSL ser

Routine

MEDIUM 5.4DOWNGRADE

CVE-2014-5799 is a medium-severity flaw (CVSS 5.4) affecting smart card. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The smart.card (aka nh.smart.card) application 3.2 for Android 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

No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	5.4 (Medium)
EPSS exploit chance	0.3% (top 78%)
CISA exploited list	No
Weakness	CWE-310
Published	2014-09-09
Last modified	2026-06-17

Publisher (CNA): CERT/CC · Vendor: nonghyup

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

Am I affected?

Timeline

2014-09-09 10:55 UTCPublished CVE record published
2026-06-17 00:12 UTCUpdated Record last modified

nonghyup smart card DOWNGRADE

Affected: 3.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.2

1. Check installed version

apt-cache policy smart-card || rpm -q smart-card || smart-card --version

2. No fixed release: DOWNGRADE to a release before 3.2 (Debian / Ubuntu)

apt-cache madison smart-card sudo apt install smart-card=<VERSION_BEFORE_3.2> sudo apt-mark hold smart-card

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list smart-card sudo dnf downgrade smart-card-<VERSION_BEFORE_3.2> sudo dnf versionlock add smart-card

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-2014-5799?

smart card: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2014-5799 being exploited?

CVE-2014-5799 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-2014-5799 affect?

CVE-2014-5799 affects smart card. Severity is medium (CVSS 5.4). The smart.card (aka nh.smart.card) application 3.2 for Android 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.

How urgent is CVE-2014-5799?

Priority 25/100. No elevated risk signals yet.

Software pages

Android vulnerabilities

References

← Back to latest CVEs