CVE-2014-5902
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 UA Cinemas - Mobile ticketing (aka com.mtel.uacinemaapps) application 2.9 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 UA Cinemas Android mobile ticketing application version 2.9 fails to validate X.509 SSL/TLS certificates from servers, allowing man-in-the-middle attackers to intercept encrypted communications by presenting forged 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= 2.9CVSS 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 UA Cinemas app is installedOn the Android device, go to Settings > Apps > Apps manager and search for 'Uacinemas' or 'UA Cinemas', or use ADB command: adb shell pm list packages | grep -i uacinemasAffected if The package com.uacinemas.mobile or similar is present on the device
-
Verify the installed application versionIn Settings > Apps > UA Cinemas app > App info, check the version number listed under 'Version' or 'Version name'; alternatively use ADB: adb shell dumpsys package <package_name> | grep versionNameAffected if The version displayed is 2.9 exactly
-
Inspect SSL certificate validation implementationDecompile the APK using tools like apktool, then examine the source code for custom TrustManager implementations, SSLContext usage with custom X509TrustManager, or verify if hostname verification is disabled via setHostnameVerifier with ALLOW_ALL_HOSTNAME_VERIFIERAffected if The code uses a custom TrustManager that does not validate the certificate chain, or uses TrustManager that accepts all certificates, or hostname verification is set to allow all hosts
A user is affected if the UA Cinemas Mobile Ticketing app version 2.9 is installed on their Android device and the app does not perform proper SSL/TLS certificate validation, allowing potential interception of sensitive user data in transit.
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 including hostname verification and certificate chain trust validation, preferably using Android's Network Security Config or a properly configured custom TrustManager.
- Consultation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-5902 — 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-5902 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