dbcve.org
Aihce 2014Application · Core Apps

CVE-2014-6929

MEDIUM · 5.4 CVSS v2.0 Published 2014-10-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
The AIHce 2014 (aka com.coreapps.android.followme.aihce2014) application 6.1.0.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.

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 confidence

The AIHce 2014 Android application (version 6.1.0.0) fails to validate X.509 certificates during SSL/TLS connections, allowing attackers on the same network to perform man-in-the-middle attacks and intercept sensitive data by presenting forged certificates.

MitigationImplement proper SSL certificate chain validation in the Android application using a custom TrustManager or certificate pinning to ensure the app only trusts legitimate server certificates.

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
Aihce 2014Application
Affected:= 6.1.0.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if AIHce 2014 app is installed
    On the Android device, go to Settings > Apps > All Apps, or use adb command: `adb shell pm list packages | grep aihce`
    Affected if The package com.aihce.year2014 or similar AIHce app package is found on the device
  2. Identify the installed version of AIHce 2014
    In Settings > Apps > AIHce 2014 > App info, view the Version field; or use adb: `adb shell dumpsys package <package_name> | grep versionName`
    Affected if The version listed is exactly 6.1.0.0
  3. Confirm the app uses network connectivity
    Review app permissions in Settings > Apps > AIHce 2014 > Permissions, or check that the app has INTERNET permission via: `adb shell dumpsys package <package_name> | grep -i android.permission.INTERNET`
    Affected if The app has INTERNET permission enabled (required for the SSL MITM flaw to be exploitable)

If AIHce 2014 version 6.1.0.0 is installed with network permission, the app is affected because it does not validate X.509 certificates during SSL/TLS connections, allowing MITM attacks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper SSL certificate chain validation in the Android application using a custom TrustManager or certificate pinning to ensure the app only trusts legitimate server certificates.

Fix this in Aihce 2014 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-6929 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-6929 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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