CVE-2014-6021
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Harley-Davidson Visa (aka com.usbank.icsmobile.harleydavidson) application 1.18 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Harley-Davidson Visa Android application version 1.18 fails to validate X.509 certificates from SSL servers, allowing man-in-the-middle attackers to intercept encrypted communications by presenting a crafted (likely self-signed or fraudulent) certificate. This enables credential theft and session hijacking since the app trusts any certificate without verification.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.18CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:A/AC:M/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed HD Visa app versionOn the Android device, go to Settings > Apps > HDvisa Harley Davidson Visa, or use 'adb shell dumpsys package com.hd.visa' to retrieve the versionName and versionCodeAffected if The version is exactly 1.18 (versionName = 1.18)
-
Confirm the app package nameList installed packages using 'adb shell pm list packages | grep -i visa' or check the app listing in Settings > AppsAffected if The package name matches the vulnerable application (typically com.hd.visa or similar Harley Davidson Visa package)
-
Verify network permission grantedCheck the app manifest using 'aapt dump badging <apk_path>' or 'adb shell dumpsys package <package_name>' to see if INTERNET permission is grantedAffected if The app has INTERNET permission, which is required for the MITM attack surface to exist
-
Inspect SSL/TLS implementation in the APKDecompile the APK using apktool or jadx, then search the source code for TrustManager,HostnameVerifier, or SSLContext implementations that bypass certificate validationAffected if Code contains custom TrustManager that accepts all certificates (e.g., trustAllCerts, empty checkServerTrusted), or disables certificate validation
-
Assess traffic interception capabilityConfigure a proxy (e.g., Burp, Charles) on the network and attempt to intercept traffic from the app with a self-signed certificateAffected if The app successfully transmits data through the proxy without certificate warnings or failures, confirming it trusts untrusted certificates
The environment is affected if the Harley-Davidson Visa Android application version 1.18 is installed and the app accepts self-signed or invalid SSL certificates during network communication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper SSL/TLS certificate validation using a correctly configured TrustManager that validates the full certificate chain, optionally supplemented with certificate pinning for sensitive endpoints.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-6021 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-6021 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data