CVE-2014-7494
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 Kontan Kiosk (aka com.appsfoundry.scoopwl.id.kontankiosk) application @7F07025E 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 Kontan Kiosk Android application fails to validate X.509 certificates from SSL servers, enabling man-in-the-middle attackers to intercept encrypted communications by presenting forged certificates and obtain sensitive information.
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= \@7f07025eCVSS 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.
-
Verify Kontan Kiosk app is installedOn the Android device, go to Settings > Apps > Apps manager and search for 'Kontan Kiosk' or 'Getscoop Kontan Kiosk'. Alternatively, use ADB command: adb shell pm list packages | grep -i kontanAffected if The Kontan Kiosk application is found installed on the device
-
Determine installed app versionIn Settings > Apps > Kontan Kiosk, look for a Version field. The affected version is identified by the build identifier 7f07025e (may appear as a version code or build number). Alternatively, use ADB: adb shell dumpsys package com.getscoop.kontan (replace package name if different)Affected if The installed version matches or contains 7f07025e as the version identifier
-
Identify if app transmits sensitive dataReview the app's functionality and network traffic. Check if the app handles financial data, login credentials, personal information, or other sensitive data that would be transmitted over the networkAffected if The app transmits sensitive user data over the network while using the vulnerable certificate validation
-
Confirm SSL/TLS certificate validation gapThis requires static analysis of the app binary or dynamic testing. For static analysis: decompile the APK and examine the code that handles HTTPS connections (look for custom TrustManager implementations or cases where validation is disabled). For dynamic testing: use a proxy like Burp Suite with an invalid certificate and observe if the app accepts itAffected if The app accepts invalid or forged SSL certificates without proper validation, allowing MITM attacks
A user is affected if the Kontan Kiosk Android app with version identifier 7f07025e is installed and the app transmits sensitive data over HTTPS without proper X.509 certificate chain 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/TLS certificate chain validation in the Android app using standard trust manager configuration, or migrate to a secure version of the application that performs certificate validation.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-7494 — 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-7494 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