dbcve.org
Thanodi Setswana TranslatorApplication · Intellegere

CVE-2014-6806

MEDIUM · 5.4 CVSS v2.0 Published 2014-09-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
The Thanodi - Setswana Translator (aka com.thanodi.thanodi) application 1.0.0 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 confidence

The Thanodi - Setswana Translator Android app version 1.0.0 fails to validate X.509 certificates when establishing SSL/TLS connections, enabling man-in-the-middle attackers to intercept communications by presenting fraudulent certificates and capture sensitive data.

MitigationImplement proper SSL certificate validation including chain-of-trust verification, hostname checking, and optionally certificate pinning for critical endpoints.

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
Thanodi Setswana TranslatorApplication
Affected:= 1.0.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm the exact installed version of the app
    On the Android device, go to Settings > Apps > find 'Thanodi - Setswana Translator' (or 'Intellegere Thanodi') and check the version number listed under App Info. Alternatively, use command 'adb shell dumpsys package com.intellegere.thanodi' (package name may vary) to retrieve version info.
    Affected if The installed version is exactly 1.0.0
  2. Identify the package name and APK
    Use 'adb shell pm list packages | grep -i thanodi' or 'adb shell pm list packages | grep -i intellegere' to find the installed package name, then locate the APK via 'adb shell pm path <package_name>' to retrieve the APK file path.
    Affected if The APK corresponds to the affected version 1.0.0 of Intellegere Thanodi Setswana Translator
  3. Inspect SSL/TLS implementation in the app
    Decompile the APK (using tools like apktool, jadx, or androguard) and examine the source code for SSL/TLS connection handling. Search for uses of TrustManager,HostnameVerifier, or custom X509TrustManager implementations. Look for code that establishes HTTPS connections (HttpsURLConnection, HttpClient, OkHttpClient) and check if certificate validation is properly implemented.
    Affected if The code shows missing or improper certificate validation (e.g., empty TrustManager, disabled hostname verification, or accepting all certificates)
  4. Test for certificate validation bypass
    Set up a man-in-the-middle proxy (such as Burp Suite, OWASP ZAP, or mitmproxy) with a self-signed or untrusted certificate. Configure the Android device to trust the proxy's CA certificate. Launch the Thanodi app and attempt to trigger network activity (e.g., use the translation feature). Observe whether the app successfully connects through the proxy without certificate warnings or failures.
    Affected if The app successfully establishes SSL/TLS connections through the proxy with an untrusted certificate, indicating certificate validation is not enforced

The environment is affected if the installed app version is exactly 1.0.0 of Intellegere Thanodi Setswana Translator and the app accepts untrusted/invalid SSL certificates without proper X.509 validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper SSL certificate validation including chain-of-trust verification, hostname checking, and optionally certificate pinning for critical endpoints.

Fix this in Thanodi Setswana Translator Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-6806 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-6806 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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