dbcve.org
Ganma\!Application · Comicsmart

CVE-2015-7785

MEDIUM · 5.9 CVSS v3.0 Published 2017-09-25
Fix available
A fix is available. Upgrade to after 2.0.9 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable 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
GANMA! App for iOS does not verify SSL certificates.

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 GANMA! iOS application fails to validate SSL certificates when establishing HTTPS connections, allowing an attacker to intercept communications via a Man-in-the-Middle (MITM) attack. This occurs because the app does not properly verify the server's certificate chain, enabling credential theft, session hijacking, and data manipulation.

MitigationImplement proper SSL/TLS certificate validation in the iOS app, preferably using certificate pinning to ensure connections are made only to legitimate servers.

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
Ganma\!Application
Affected:<= 2.0.9

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
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

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 Comicsmart Ganma! app is installed
    Check your iOS device for the Comicsmart Ganma! or GANMA! application in your installed apps list
    Affected if The app is present on the device
  2. Determine installed app version
    Open the App Store, go to your purchased apps list, or check the app's App Store page for the version number. Alternatively, check the app version in Settings > General > iPhone Storage > GANMA if available
    Affected if Version displays as 2.0.9 or lower
  3. Verify affected version range
    Compare your installed version against the affected range: any version <= 2.0.9
    Affected if Your version number is 2.0.9 or any lower numbered version
  4. Assess usage of HTTPS features
    Note that the vulnerability applies when the app makes any HTTPS connection to its servers, regardless of specific feature usage
    Affected if You use the app to access content or user accounts via the internet

You are affected if Comicsmart Ganma! version 2.0.9 or lower is installed on your iOS device and you use the app to connect to its servers.

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
Upgrade available Upgrade to a release after 2.0.9
Interim mitigation

Implement proper SSL/TLS certificate validation in the iOS app, preferably using certificate pinning to ensure connections are made only to legitimate servers.

Fix this in Ganma\! Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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