CVE-2015-8287
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 · uneditedSwann SRNVW-470LCD devices with firmware through 0114 and SWNVW-470CAM devices with firmware through 1022 allow remote attackers to watch live video by visiting an unspecified URL.
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 · moderate confidenceSwann SRNVW-470LCD and SWNVW-470CAM surveillance cameras with firmware through versions 0114 and 1022 respectively contain an authentication bypass vulnerability allowing remote unauthenticated attackers to access live video streams by visiting a specific (unspecified) URL on the web interface.
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<= 1022<= 0114CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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.
-
Identify the camera modelAccess the camera's web interface or check the physical device label to confirm the exact model number is either SRNVW-470LCD or SWNVW-470CAMAffected if The model is SRNVW-470LCD or SWNVW-470CAM
-
Check the installed firmware versionLog into the camera's web interface and navigate to the System or Settings menu to view the firmware version. Compare this version against the affected ranges: SRNVW-470LCD <= 0114 or SWNVW-470CAM <= 1022Affected if The firmware version is 0114 or lower for SRNVW-470LCD, or 1022 or lower for SWNVW-470CAM
-
Verify network exposure of the web interfaceDetermine if the camera's web interface (typically on ports 80 or 8080) is accessible from networks outside your trusted internal network. Check firewall rules, NAT configurations, or port forwarding settings that expose the deviceAffected if The web interface is reachable from untrusted networks or the internet without VPN or firewall filtering
-
Test for unauthenticated video stream accessUsing a web browser or video client, attempt to access common video stream URLs on the camera such as /videostream.html, /live.htm, or /stream without providing any login credentialsAffected if Video streams are accessible without authentication prompts or credentials
A user is affected if they have a SRNVW-470LCD or SWNVW-470CAM camera with firmware at or below the affected version numbers AND the web interface is accessible from untrusted networks, allowing unauthenticated access to video feeds.
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 dataRestrict network exposure of affected devices behind firewalls or VPNs, implement IP-based access controls, and contact Swann for patched firmware. Until fixed, monitor for unauthorized access to video feeds.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-8287 — 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-8287 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