CVE-2016-8507
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 · uneditedYandex Browser for iOS before 16.10.0.2357 does not properly restrict processing of facetime:// URLs, which allows remote attackers to initiate facetime-call without user's approval and obtain video and audio data from a device via a crafted web site.
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 confidenceYandex Browser for iOS before version 16.10.0.2357 fails to properly restrict processing of facetime:// URL schemes. This allows malicious webpages to trigger FaceTime calls without user interaction, potentially exposing device video and audio data to remote attackers.
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< 16.10.0.2357CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Verify Yandex Browser for iOS is installedCheck the iOS device for the Yandex Browser app icon on the home screen, or navigate to Settings > General > iPhone Storage (or Settings > Apps on newer iOS) and look for Yandex Browser in the app list.Affected if The app is not present on the device - if absent, this CVE does not apply.
-
Determine the installed version numberOpen the App Store app, tap your profile icon, scroll to Purchased, search for Yandex Browser, and view the version information. Alternatively, check Settings > General > iPhone Storage > Yandex Browser (or Settings > Apps > Yandex Browser on newer iOS) to see the version number listed under the app name.Affected if Version information cannot be retrieved - the detection is inconclusive.
-
Compare version against the affected rangeTake the version number identified in the previous step and compare it numerically to 16.10.0.2357. Any version lower than 16.10.0.2357 (such as 16.9.x, 16.8.x, or earlier) falls within the affected range.Affected if The installed version is less than 16.10.0.2357 - the device is vulnerable to unauthenticated FaceTime call initiation.
A user is affected if Yandex Browser for iOS is installed with a version number lower than 16.10.0.2357, as this version threshold is the boundary where proper facetime:// URL scheme validation was implemented.
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 data16.10.0.2357
Upgrade Yandex Browser for iOS to version 16.10.0.2357 or later which implements proper validation of facetime:// URL schemes before execution.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-8507 — 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-2016-8507 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