CVE-2017-14582
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 · uneditedThe Zoho Site24x7 Mobile Network Poller application before 1.1.5 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 self-signed 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 confidenceThe Zoho Site24x7 Mobile Network Poller Android application before version 1.1.5 fails to validate X.509 certificates from SSL/TLS servers, accepting any certificate presented including self-signed ones. This allows an attacker positioned on the network path to intercept encrypted traffic by presenting a fraudulent certificate, enabling man-in-the-middle attacks and exposure of sensitive data transmitted by 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<= 1.1.4CVSS 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.
-
Locate the installed applicationOpen Android Settings > Apps > Apps, then search for 'Site24x7 Mobile Network Poller' in the list of installed applications. Alternatively, use ADB command: `adb shell pm list packages | grep site24x7`Affected if The application is not found in the installed apps list - the vulnerability does not apply as the app is not installed
-
Determine the installed versionTap on Site24x7 Mobile Network Poller in the apps list, then view the 'App info' or 'Version' field under 'App version' or 'Version info'. Alternatively, use ADB: `adb shell dumpsys package com.site24x7.mnp` and look for versionName in the outputAffected if Unable to determine the version number - manual verification required
-
Compare against vulnerable version rangeCheck if the installed version number is 1.1.4 or any version lower (for example: 1.1.3, 1.1.2, 1.1.1, 1.1.0, 1.0.x, etc.)Affected if Installed version is 1.1.4 or lower - the app does not validate SSL/TLS certificates and is vulnerable to MITM attacks
If the Site24x7 Mobile Network Poller Android app is installed at version 1.1.4 or earlier, the vulnerability is present because the app accepts any SSL/TLS certificate without validation.
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 dataUpdate Zoho Site24x7 Mobile Network Poller to version 1.1.5 or later, which implements proper X.509 certificate validation to prevent MITM attacks.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14582 — 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-14582 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