dbcve.org
MintegraladsdkApplication · Mintegral

CVE-2020-7705

HIGH · 8.1 CVSS v3.1 Published 2020-08-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges

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
This affects the package MintegralAdSDK from 0.0.0. The SDK distributed by the company contains malicious functionality that tracks any URL opened by the app and reports it back to the company, along with performing advertisement attribution fraud. Mintegral can remotely activate hooks on the UIApplication, openURL, SKStoreProductViewController, loadProductWithParameters and NSURLProtocol methods along with anti-debug and proxy detection protection. If those hooks are active MintegralAdSDK sends obfuscated data about every opened URL in an application to their servers. Note that the malicious functionality is enabled even if the SDK was not enabled to serve ads.

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 MintegralAdSDK contains hidden malicious functionality that remotely hooks iOS URL handling methods (UIApplication openURL, SKStoreProductViewController, loadProductWithParameters, NSURLProtocol) to intercept and exfiltrate all URL activity from the host application to Mintegral servers, performing advertisement attribution fraud even when the SDK is not enabled for ad serving.

MitigationRemove the MintegralAdSDK from any applications that include it, as the malicious functionality cannot be safely disabled and operates regardless of SDK configuration. Audit for any applications that may have bundled this SDK.

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
MintegraladsdkApplication
Affected:>= 0.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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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. Inspect application bundle for MintegralAdSDK framework
    Extract the IPA or examine the application bundle contents. Look for a framework or library file named MintegralAdSDK.framework, libMintegralAdSDK.a, or similar Mintegral-related binaries in the Frameworks or Libraries folder.
    Affected if The MintegralAdSDK framework or library file is present in the application bundle.
  2. Review linked frameworks and libraries
    Use tools like otool -L on the main binary, or check the project's Linked Frameworks and Libraries section in Xcode. Search for any frameworks or libraries with 'Mintegral' in the name.
    Affected if MintegralAdSDK or any Mintegral-related framework is linked to the application.
  3. Search binary for Mintegral class references
    Use strings or similar tools on the compiled binary to search for class prefixes commonly used by Mintegral, such as 'MTG' or 'Mintegral'. Run: strings <app_binary> | grep -i mintegral
    Affected if The binary contains references to Mintegral-specific classes or symbols.
  4. Check Podfile or Carthage dependencies
    Examine the project's dependency manager configuration files (Podfile, Cartfile, or Package.swift) for any Mintegral-related dependencies.
    Affected if The project configuration includes MintegralAdSDK as a dependency.

If the MintegralAdSDK is present in the application bundle or linked as a dependency in any version, the environment is affected because the malicious functionality operates regardless of SDK configuration.

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

Remove the MintegralAdSDK from any applications that include it, as the malicious functionality cannot be safely disabled and operates regardless of SDK configuration. Audit for any applications that may have bundled this SDK.

Fix this in Mintegraladsdk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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