Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2014-6877: The Santander Personal Banking (aka com.sovereign.santander) application 2.1 for Android does not verify X.509

24
Routine
MEDIUM 5.4DOWNGRADE

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

The Santander Personal Banking (aka com.sovereign.santander) application 2.1 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 score5.4 (Medium)
EPSS exploit chance0.3% (top 81%)
CISA exploited listNo
WeaknessCWE-310
Published2014-10-02
Last modified2026-06-17
Publisher (CNA): CERT/CC · Vendor: santanderbank

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

santanderbank santander personal banking DOWNGRADE
Affected: 2.1
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.1
1. Check installed version
apt-cache policy santander-personal-banking || rpm -q santander-personal-banking || santander-personal-banking --version
2. No fixed release: DOWNGRADE to a release before 2.1 (Debian / Ubuntu)
apt-cache madison santander-personal-banking sudo apt install santander-personal-banking=<VERSION_BEFORE_2.1> sudo apt-mark hold santander-personal-banking
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list santander-personal-banking sudo dnf downgrade santander-personal-banking-<VERSION_BEFORE_2.1> sudo dnf versionlock add santander-personal-banking
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-6877?

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

Is CVE-2014-6877 being exploited?

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

CVE-2014-6877 affects santander personal banking. Severity is medium (CVSS 5.4). The Santander Personal Banking (aka com.sovereign.santander) application 2.1 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 c

How urgent is CVE-2014-6877?

Priority 24/100. No elevated risk signals yet.

Software pages

Android 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.