CVE-2012-5810: n/a vulnerability

CVE-2012-5810: The Chase mobile banking application for Android does not verify that the server hostname matches a domain...

The Chase mobile banking application for Android does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate, related to overriding the default X509TrustManager. NOTE: this vulnerability was fixed in the summer of 2012, but the version number was not changed or is not known.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 6, 2024, 21:14 UTC (UTC+00:00)

Security readout for executives and security teams

This was an Android Chase mobile banking app TLS validation flaw. The app could accept a valid certificate for the wrong hostname, allowing a network attacker to impersonate the banking server. The source says it was fixed in summer 2012, but the exact fixed version is unknown. Exposure appears limited to legacy Chase Android mobile banking app builds from before the summer 2012 fix. The affected version number is not provided, so exposure cannot be confirmed from version metadata alone. Treat as a historical issue unless legacy Android app builds remain in use or archived for deployment. Priority rises for financial-services environments managing old mobile devices or app packages. Mitigation focus: Use only the current official Chase Android application from trusted app stores.; Remove archived or sideloaded legacy Chase Android APKs from managed devices.; Check Chase or app-store guidance for supported and fixed mobile app versions..

Prepared: Jun 24, 2026, 12:04 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2012-5810 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Nov 4, 2012, 22:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
https://docs.google.com/document/pub?id=1roBIeSJsYq3Ntpf6N0PIeeAAvu4ddn7mGo6Qb7aL7ewCVE reference · x_refsource_MISC

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.