dbcve.org
Mapa Da MinaApplication · Elsio

CVE-2014-7359

MEDIUM · 5.4 CVSS v2.0 Published 2014-10-19
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 MAPA DA MINA (aka com.wMAPADAMINA) application 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 confidence

The MAPA DA MINA Android application (version 0.1) fails to validate X.509 certificates when establishing SSL/TLS connections with remote servers. This allows man-in-the-middle attackers to intercept communications by presenting forged certificates, enabling them to spoof servers and capture sensitive data transmitted by the application.

MitigationImplement proper SSL certificate chain validation using Android's standard TrustManager or certificate pinning to ensure the app only accepts certificates from trusted, legitimate CAs.

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
Mapa Da MinaApplication
Affected:= 0.1

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. Identify if the app is installed
    On the Android device, go to Settings > Apps > Application Manager (or Apps) and look for an app named 'Mapa Da Mina', 'MAPA DA MINA', or 'Elsio Mapa Da Mina'. Alternatively, use adb: 'adb shell pm list packages' to list all installed packages and search for any containing 'mapa' or 'mina'.
    Affected if The application is found on the device with the name matching the affected product.
  2. Verify the installed version
    In Settings > Apps > [Mapa Da Mina] > App info, check the version number. It should display as '0.1' or version code 1. Use adb: 'adb shell dumpsys package [package_name]' to get version details.
    Affected if The version listed is exactly 0.1.
  3. Confirm the app handles sensitive data
    Review the app's functionality and permissions. Check if it transmits user credentials, personal information, financial data, or other sensitive content over the network. Examine AndroidManifest.xml for network-related permissions (INTERNET, ACCESS_NETWORK_STATE).
    Affected if The app has network permissions and processes sensitive user data.
  4. Check for SSL validation implementation
    Analyze the application APK (obtain via 'adb pull /data/app/[package_name].apk' or use a rooting method) using static analysis tools (like jadx, apktool, or MobSF). Search the decompiled source code for TrustManager implementation, hostname verification (HostnameVerifier), and certificate validation calls. Look for custom TrustManager that accepts all certificates or disables validation.
    Affected if The code shows no proper certificate validation (e.g., custom TrustManager that trusts all certs, or validation is commented out/disabled) in network communication classes.

A user is affected if the Mapa Da Mina application version 0.1 is installed on their Android device and the app transmits sensitive data over the network without proper SSL/TLS certificate 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 chain validation using Android's standard TrustManager or certificate pinning to ensure the app only accepts certificates from trusted, legitimate CAs.

Fix this in Mapa Da Mina 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-7359 — 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-7359 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