CVE-2014-7075: The HAPPY (aka com.tw.knowhowdesign.sinfonghuei) application 2.0 for Android does not verify X.509 certificate

Routine

MEDIUM 5.4DOWNGRADE

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

The HAPPY (aka com.tw.knowhowdesign.sinfonghuei) application 2.0 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	1.1% (top 34%)
CISA exploited list	No
Weakness	CWE-310
Published	2014-10-19
Last modified	2026-06-17

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

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

Am I affected?

Timeline

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

happycloud happy DOWNGRADE

Affected: 2

Fixed in: no fixed release known

Safe to downgrade to: a release before 2

1. Check installed version

apt-cache policy happy || rpm -q happy || happy --version

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

apt-cache madison happy sudo apt install happy=<VERSION_BEFORE_2> sudo apt-mark hold happy

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

dnf --showduplicates list happy sudo dnf downgrade happy-<VERSION_BEFORE_2> sudo dnf versionlock add happy

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-7075?

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

Is CVE-2014-7075 being exploited?

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

CVE-2014-7075 affects happy. Severity is medium (CVSS 5.4). The HAPPY (aka com.tw.knowhowdesign.sinfonghuei) application 2.0 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 certi

How urgent is CVE-2014-7075?

Priority 35/100. No elevated risk signals yet.

Software pages

Android vulnerabilities

References

← Back to latest CVEs