CVE-2014-6006
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 Gratta & Vinci? (aka com.dreamstep.wGrattaevinci) application 0.21.13167.93474 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 Android application Gratta & Vinci fails to validate X.509 certificates from SSL/TLS servers, enabling man-in-the-middle attackers to intercept encrypted communications, spoof legitimate servers, and steal sensitive data transmitted by the application.
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= 0.21.13167.93474CVSS 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 Gratta & Vinci app is installedOn the Android device, go to Settings > Apps > look for 'Gratta & Vinci' in the app list, or run 'pm list packages | grep gratta' via ADB shellAffected if The app is present on the device and is used for lottery/scratch card functionality involving network transactions
-
Identify the installed version numberIn Settings > Apps > Gratta & Vinci, scroll to the 'Version' field under 'App info', or run 'dumpsys package com.grattaevinci.app | grep versionName' via ADB shellAffected if The version shown matches 0.21.13167.93474 exactly, indicating this specific vulnerable build
-
Determine if the app transmits sensitive dataMonitor network traffic from the app using a proxy (like Burp Suite) or check app permissions for network access via 'pm list permissions -g' and review if the app handles user credentials, payment data, or personal informationAffected if The app makes HTTP/HTTPS requests to backend servers while missing proper certificate chain validation, allowing MITM interception of that traffic
-
Verify SSL certificate validation is bypassedInstall the app APK, decompile it using tools like jadx or apktool, and inspect the network code for TrustManager implementations or check if the SSLSocketFactory is created with a custom trust store that accepts all certificatesAffected if The app contains code that implements a custom X509TrustManager that overrides default certificate validation or accepts all certificates unconditionally
You are affected if Gratta & Vinci version 0.21.13167.93474 is installed and the app transmits sensitive user data over network connections without proper SSL/TLS 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/TLS certificate validation in the application's network stack, including certificate chain verification, hostname validation, and optionally certificate pinning for critical endpoints.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-6006 — 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-6006 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