CVE-2015-5655
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 Adways Party Track SDK before 1.6.6 for iOS 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 confidenceThe Adways Party Track SDK before version 1.6.6 for iOS fails to validate X.509 certificates from SSL servers, allowing man-in-the-middle attackers on the same network path to intercept and spoof server communications and obtain sensitive information.
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.6.5CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:M/Au:N/C:P/I:P/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 Adways Party Track SDK in your iOS projectSearch your project directory for files or folders named 'AdwaysPartyTrack', 'PartyTrack', or similar variants. Check your CocoaPods Podfile, CocoaPods Pods folder, or Carthage dependencies if used.Affected if The SDK files are present in the project
-
Identify the installed SDK versionCheck the SDK's version header file, podspec, or any version configuration file included with the Adways Party Track SDK. If using CocoaPods, run 'pod list' or check the Podfile.lock for the AdwaysPartyTrack entry.Affected if The version listed is 1.6.5 or earlier, or no version is specified and the SDK is present
-
Confirm network usage of the SDKReview your app's code for imports and usage of Adways Party Track SDK classes. Search for references to PTTracker, PartyTrack, or any Adways-related network configuration in your source files.Affected if The SDK is imported and used in code that handles network communications
-
Check for SSL/TLS connections in app trafficUse a network proxy tool like Charles Proxy or Burp Suite to intercept your app's traffic. Observe whether connections to Adways-related endpoints occur without proper certificate validation warnings.Affected if Your app communicates with Adways servers and SSL certificate validation is bypassed (connections succeed despite proxy CA not being trusted)
-
Review third-party SDK audit logs or reportsIf your organization maintains an SDK inventory or conducts security audits, check those records for the Adways Party Track SDK version and any associated risk assessments.Affected if Records show the SDK at version 1.6.5 or below is included in your iOS application
Your environment is affected if the Adways Party Track SDK version 1.6.5 or earlier is present in your iOS project and your app uses it for network communications.
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 dataUpgrade the Adways Party Track SDK to version 1.6.6 or later which implements proper X.509 certificate validation; if the SDK is no longer needed, remove it entirely.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5655 — 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-2015-5655 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