CVE-2014-5949
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 TICKET APP - Concerts & Sports (aka com.xcr.android.ticketapp) application 3.0.1 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 TICKET APP for Android version 3.0.1 fails to verify X.509 certificates from SSL servers, allowing man-in-the-middle attackers to intercept traffic by presenting crafted certificates. This enables credential theft, session hijacking, and data manipulation.
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= 3.0.1CVSS 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 the app is installedOn the Android device, go to Settings > Apps > Downloaded or All Apps, and search for 'Mobileticketapp Ticket App Concerts & Sports' or 'Ticket App'. Alternatively, use adb shell pm list packages to list all installed packages.Affected if The app 'Mobileticketapp Ticket App Concerts & Sports' is present on the device
-
Check the installed versionIn Settings > Apps > App Info, locate the app and view its version information (typically shown as 'Version X.X.X' or 'Ver X.X.X'). Alternatively, use adb shell dumpsys package <package_name> to retrieve version details.Affected if The installed version is exactly 3.0.1
-
Confirm SSL certificate validation is missingSince this is a code-level vulnerability in the app itself, perform traffic analysis: configure a proxy like Burp Suite or Charles on a test device, install the proxy CA certificate on the device, and attempt to intercept traffic from the app. Alternatively, review the app's source code (if available) for proper implementation of X509TrustManager and hostname verification.Affected if The app successfully connects through the proxy without certificate warnings, or code review reveals missing certificate chain verification and hostname validation in the network implementation
A user is affected if the Android app 'Mobileticketapp Ticket App Concerts & Sports' version 3.0.1 is installed and it transmits data without properly validating SSL server certificates, allowing intercepted credentials and sessions.
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 application, including certificate chain verification, hostname validation, and optionally certificate pinning to ensure connections are made to legitimate servers.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-5949 — 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-5949 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