dbcve.org
Motor Town\Application · Alawar

CVE-2014-7670

MEDIUM · 5.4 CVSS v2.0 Published 2014-10-21
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 Motor Town: Machine Soul Free (aka com.alawar.motortownfree) application 1.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 Android application Motor Town: Machine Soul Free version 1.1 fails to validate X.509 certificates during SSL/TLS connections, allowing man-in-the-middle attackers to intercept encrypted communications by presenting forged certificates and spoof the legitimate server.

MitigationThe application must be updated to implement proper SSL certificate validation, typically through certificate pinning or a correctly configured TrustManager that validates the entire certificate chain.

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
Motor Town\Application
Affected:= _machine_soul_free

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. Verify if Motor Town: Machine Soul Free is installed
    Open Android Settings > Apps > Applications Manager and search for 'Motor Town' or 'Machine Soul Free', or use ADB command: pm list packages | grep -i 'motor' or 'machine_soul'
    Affected if The application is present on the device
  2. Determine the installed version of the app
    In Settings > Apps > Motor Town: Machine Soul Free > Version info, or use ADB: dumpsys package com.alawar.motortown (replace with actual package name if different)
    Affected if The installed version is 1.1 or falls within the affected product range (Alawar Motor Town: machine_soul_free)
  3. Inspect the application's SSL/TLS implementation
    Analyze the APK file (obtain via ADB: adb pull /data/app/[package]/base.apk) using a decompiler such as jadx or apktool. Navigate to the network or HTTP client code and examine whether X509TrustManager or HostnameVerifier is properly implemented with full certificate chain validation
    Affected if The code shows custom TrustManager that accepts all certificates, or lacks proper certificate chain validation, or uses an insecure implementation that does not validate the entire X.509 certificate chain
  4. Test for certificate validation bypass
    Set up a proxy (such as Burp Suite or OWASP ZAP) with a self-signed certificate and attempt to intercept traffic from the app. Observe whether the app accepts the proxy certificate without warning or error
    Affected if The app successfully connects through the proxy with an untrusted/frogery certificate, indicating SSL validation is not properly occurring
  5. Verify if the app uses certificate pinning
    Search the decompiled APK code for implementations of CertificatePinner, custom pinning logic, or checks for specific certificate public keys or subject DNs
    Affected if No certificate pinning mechanism is found and the app accepts connections to arbitrary servers with forged certificates

The environment is affected if Motor Town: Machine Soul Free version 1.1 (or the affected version range) is installed and the application does not properly validate X.509 certificate chains during SSL/TLS connections, which can be confirmed by code inspection or successful MITM proxy interception.

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

The application must be updated to implement proper SSL certificate validation, typically through certificate pinning or a correctly configured TrustManager that validates the entire certificate chain.

Fix this in Motor Town\ Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-7670 — 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-7670 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