CVE-2014-7402
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 SK encar (aka com.encardirect.app) application @7F050000 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 SK encar Android application (com.encardirect.app) fails to validate X.509 certificates from SSL servers, allowing man-in-the-middle attackers to intercept encrypted communications by presenting fraudulent certificates and steal sensitive user data.
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= \@7f050000CVSS 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.
-
Check if Encardirect app is installedOn Android device, go to Settings > Apps > All, or use adb command: pm list packages | grep encardirect. Look for package name com.encardirect.appAffected if The package com.encardirect.app is not found on the device - not affected
-
Verify installed app versionOn Android device, go to Settings > Apps > Encardirect Sk Encar > App info, or use: pm dump com.encardirect.app | grep versionName. Check if version matches 7f050000Affected if The installed version is exactly 7f050000 - this is the vulnerable version
-
Confirm certificate validation behavior (requires traffic inspection)Set up a proxy (such as Burp Suite or OWASP ZAP) to intercept SSL traffic from the device. Install the proxy CA certificate on the Android device. Launch the Encardirect app and attempt to authenticate or perform network actionsAffected if The app successfully connects through the proxy without certificate warnings or failures, indicating it does NOT validate SSL certificates properly - vulnerable to MITM
-
Check for existing SSL/TLS inspection setupReview network configuration on the device. If a corporate MDM or security solution is intercepting SSL traffic, the app may be silently trusting the intercepted certificatesAffected if SSL interception is active and the app functions normally without certificate errors - the app is vulnerable to certificate validation bypass
User is affected if the Encardirect Sk Encar app (com.encardirect.app) version 7f050000 is installed and the app accepts SSL connections without proper certificate validation.
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 certificate validation by using certificate pinning or ensuring the application validates certificates against a trusted CA store when establishing SSL/TLS connections.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-7402 — 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-7402 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