CVE-2014-5913
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 Allies in War (aka com.gamelion.aiw) application 1.3.2 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 Allies in War Android application version 1.3.2 fails to validate X.509 certificates when establishing SSL/TLS connections. This allows attackers on the same network to perform man-in-the-middle attacks by presenting fraudulent certificates, enabling interception of sensitive data transmitted between the app and servers.
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.3.2CVSS 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 if Allies in War app is installedLocate the app on the Android device. Check the application list for 'Allies in War' or 'Allies In War' by Game Lion. This can be done via Settings > Apps on the device, or using ADB with 'adb shell pm list packages' to list all installed packages.Affected if The app 'Allies in War' by Game Lion is present on the device
-
Determine the installed version numberOpen Settings > Apps > Allies in War (or Allie in War) and view the Version info, or use 'adb shell dumpsys package <package_name>' to retrieve detailed package information including versionName and versionCode.Affected if The version displayed is exactly 1.3.2
-
Verify app uses network communicationCheck if the app has network permissions (INTERNET, ACCESS_NETWORK_STATE) by reviewing the AndroidManifest.xml or using 'adb shell pm dump <package_name>' to view permissions. Monitor network traffic using a packet capture tool while the app is in use.Affected if The app has network permissions and transmits data over the network while the vulnerability exists
A user is affected if the Android device has Game Lion's Allies in War app installed at version exactly 1.3.2 and that app transmits sensitive data over the network without proper SSL 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 in the Android app by using a custom TrustManager that validates the certificate chain, or implement certificate pinning for known server certificates. Recompile and distribute an updated APK to users.
- 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-5913 — 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-5913 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