CVE-2017-13105
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 · uneditedHi Security Virus Cleaner - Antivirus, Booster, 3.7.1.1329, 2017-09-13, Android application accepts all SSL certificates during SSL communication. This opens the application up to a man-in-the-middle attack having all of its encrypted traffic intercepted and read by an attacker.
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 confidenceThe Hi Security Virus Cleaner Android application (v3.7.1.1329) implements a custom TrustManager that accepts all SSL certificates without validation. This allows any malicious actor on the network path to intercept, decrypt, and modify encrypted traffic by presenting a forged certificate, enabling man-in-the-middle attacks against all SSL/TLS communications from the app.
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= 3.7.1.1329CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed version of Hi Security Virus CleanerOn the Android device, go to Settings > Apps > Hi Security Virus Cleaner (or Hisecuritylab Virus Cleaner) and look at the version number under App InfoAffected if The version shown is 3.7.1.1329 exactly
-
Inspect app for custom TrustManager implementationIf you have access to the APK file, decompile it and search the source code for any class that extends TrustManager or implements X509TrustManager. Look for implementations that have empty verify methods or catch all exceptions without rethrowingAffected if A custom TrustManager class exists that accepts all certificates without throwing exceptions in the checkServerTrusted or checkClientTrusted methods
-
Check for disabled SSL validation codeDecompile the APK and search for code patterns that disable SSL validation, such as creating custom SSLSocketFactory that accepts all certificates, or setting custom TrustManager via TrustManagerFactory.init with a keystore that contains no certificatesAffected if Code exists that creates an SSLSocketFactory or TrustManager that accepts all certificates regardless of validity
-
Verify certificate chain validation behaviorUse a network proxy tool (like Burp Suite or OWASP ZAP) with a self-signed certificate to intercept traffic from the app. If the app successfully connects without certificate warnings or failures, validation is bypassedAffected if The app successfully establishes SSL/TLS connections through a proxy with an untrusted/forged certificate
You are affected if the installed version is exactly 3.7.1.1329 OR if analysis of the app's code reveals a custom TrustManager that accepts all certificates without validation, OR if the app connects through a proxy with an untrusted certificate.
Generated from the published advisory. Verify against your own configuration.
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 dataReplace the custom TrustManager with proper certificate chain validation using Android's default TrustManager or a properly configured custom implementation that validates the certificate chain, expiration, and hostname.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-13105 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-13105 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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